Let the writing lead
Build a publication with a deliberate separation between its public identity and its administrative footprint.
Content revised · English
- Architecture to evaluate
- WordPress / Ghost / static
- Prepared starting points
- 5 plans
- Responsibilities
- Application, rights and recovery
A fit shortlist, not installed software or live inventory.
Keep these in view.
- WordPress / Ghost / static.
- Review all the identity paths.
- Separate publications deliberately.
WordPress / Ghost / static
WordPress and Ghost support rich publishing but require application updates and a database backup. A static site can reduce the exposed runtime when the project does not need dynamic accounts. Choose the stack the author can maintain, then keep the public pseudonym distinct from account recovery details.
Review all the identity paths
Domain registration, historical DNS, an unproxied mail hostname and image metadata can link a publication to its origin or owner. A reverse proxy alone does not close those paths. Check document metadata and the application’s outbound mail before publishing.
Separate publications deliberately
Multiple sites on one plan share resource and account boundaries. The shared catalogue lists one website for Veil One and five for Veil Circle; a plan without a fixed site count still has resource and policy limits. Back up each publication independently and document who can administer it.
Decide what stays public
A pseudonym does not prevent links through domain registration, reused usernames, payment records or uploaded image metadata. Map those links before publishing and avoid mixing personal and editorial accounts.
Choose a manageable stack
A small static blog can use shared hosting; a custom application may need a VPS. Keep dependencies current, administration restricted and comment handling separate from the publishing process.
Protect the recovery path
An encrypted backup and a tested export matter as much as the front page. Keep recovery credentials in a secure location and remove unnecessary identifying details from drafts and media.
Capacity to consider.
Match these starting points to the representative application. Software installation and live inventory are not connected; the exact specification and period total come from the catalogue.
Veil One
Keep a single website and five mailboxes together in a compact hosting account with 5 GB of NVMe storage and 50 GB of monthly transfer. A panel-based WordPress installer and Let's Encrypt certificates support a personal site, publication or small project without managing a server operating system.
- Storage
- 5 GB NVMe SSD
- Transfer
- 50 GB / month
billed monthly
Veil Studio
Manage up to five websites and 25 mailboxes within 25 GB of NVMe storage and a 250 GB monthly transfer allowance. Daily backups with seven-day retention, SSL certificates and a CDN make this a broader foundation for several sites under one account.
- Storage
- 25 GB NVMe SSD
- Transfer
- 250 GB / month
billed monthly
Umbra 1
Run a small Linux service on one AMD EPYC virtual CPU, 2 GB of ECC memory and 25 GB of NVMe storage with full root access on KVM. The configuration pairs a 1 Gbps port with 1 TB of monthly transfer, IPv4 and IPv6, and a 10 Gbps network mitigation tier.
- Compute
- 1 vCPU (AMD EPYC)
- Memory
- 2 GB DDR4 ECC
- Storage
- 25 GB NVMe SSD
- Transfer
- 1 TB / month
billed monthly
Umbra 2
Give web applications, containers or a private tunnel two AMD EPYC virtual CPUs, 4 GB of ECC memory and 60 GB of NVMe storage. Root access on KVM, a 1 Gbps port and 3 TB of monthly transfer provide more room than the entry configuration without moving to dedicated hardware.
- Compute
- 2 vCPU (AMD EPYC)
- Memory
- 4 GB DDR4 ECC
- Storage
- 60 GB NVMe SSD
- Transfer
- 3 TB / month
billed monthly
Cipher One
Keep one mailbox with 10 GB of storage and an optional custom domain, accessible through Roundcube webmail or IMAP, POP3 and SMTP clients. PGP-compatible workflows let you choose client-side encryption, while the mailbox account itself uses the same username-based sign-up as the other services.
- Storage
- 10 GB
billed monthly
Before this workload goes live.
- Check the exact plan’s CPU, memory, disk, transfer and port.
- Choose a listed region and verify the workload’s permitted use.
- Test the representative application and an independent restore.
Questions, answered.
Will domain privacy hide the author completely?
Registrar privacy, ownership arrangements and published WHOIS/RDAP records have their own boundaries. Historical records and account/payment identifiers can still matter. Verify the registrar’s exact arrangement.
Can a proxy leak the origin?
Old DNS history, mail records, unproxied hostnames and other services on the same address may reveal it. A proxy toggle alone is not origin isolation.
Can I run several pseudonymous sites?
Match the exact hosted-site limit and shared resource boundary. Separate account administration and backups where the publications should not share one failure or identity path.
What if a topic is prohibited in a relevant jurisdiction?
Review the content, audience and applicable law before publishing. Server location does not supply universal permission, and the proposed AUP remains relevant.
What is kept in my account workspace?
Your configuration, selected plan, image, location and billing term are kept with the order and payment request references. Quotes, payment-state reads and support conversations remain linked to your account. Read fulfilment details separately from payment status.