Publish an onion service from a Swiss hosting environment. Veil pairs listed CPU, memory and SSD resources with stack choices, onion-address allowances and optional backup retention for legitimate private publishing.
A focused onion-service configuration for one address, with 2 CPU cores, 2 GB of memory and a 30 GB SSD. Traffic and database counts are listed as unlimited.
Allocate up to three onion addresses with 4 CPU cores, 4 GB of memory and a 60 GB SSD. This configuration adds capacity for separate services or a growing onion project.
A larger onion-hosting allocation for up to five addresses. Four CPU cores, 6 GB of memory and 100 GB of SSD storage provide more room for content and service data.
Compare the listed specifications and base prices. Final availability, delivery and applicable tax are confirmed on your quote. Illustrations are conceptual.
Understand what makes this service family useful.
Compare the onion-address allowance in each plan and select additional generated addresses if your project needs separate services.
The configurator includes Nginx, Apache and Node.js stack choices. Select the environment that matches your site's software and deployment method.
CPU, RAM and SSD capacity remain visible in the plan table. Onion routing does not remove the need to size the application and its data.
Daily backup options have distinct retention periods. Consider site data, database contents and service-key handling as part of your recovery plan.
Offer an onion access point for a lawful publication whose readers benefit from an alternative connection path.
Run a legitimate community or research site with an application stack appropriate to its audience and data.
Prepare an onion version of your own service while keeping application security and publishing controls consistent.
An application expecting a PHP web stack has different requirements from a Node.js service. Review the stack selector, then compare the CPU, memory and storage needed for the application and its databases. The number of onion addresses is a separate allowance, not a measure of application performance.
Review what the application reveals through pages, uploads, error messages and embedded resources. Protect administrator access and avoid exposing configuration files or credentials. Onion hosting provides a connection method; it does not establish that an application is secure or that an operator is anonymous.
Your content, database and onion-service identity may all matter when restoring a site. Define what must be backed up and who can access the copies before relying on a retention option. Veil is intended for lawful publishing and private services; fraud, abuse and harmful content remain outside its intended use.
Plan access through the onion address and avoid exposing the application through an unintended public interface. Check embedded resources, callbacks and outgoing connections that could reveal infrastructure details. Panel choice, PHP support, mail access and service-key handover need operator confirmation. A separate public website can share content through a planned publishing process without assuming Veil supplies a clearnet endpoint.
Available choices depend on the selected configuration. See included selections and option prices in the configurator.
Specific answers for this service family.
Visitors need software capable of connecting to onion services. Provide clear access instructions for your audience and test your service through a compatible connection.
The stack selector lists those environment choices for Veil. Match the selection to the application's requirements rather than choosing on the stack name alone.
No. Application behaviour, access practices, payments and data handling can expose information. The connection method is one part of the privacy design.
Each plan lists its address allowance. Additional generated addresses are an optional configuration choice and appear separately in the summary.
No. CPU, memory and storage remain defined resources, and acceptable-use requirements still apply. Traffic wording does not make every application or activity suitable.
Plan Veil as onion publishing and use a Tor-capable client. Any clearnet counterpart requires a separate reviewed deployment; the onion-address allowance does not include a public-domain endpoint.
The catalogue defines application-stack choices, not a verified aaPanel installation or mail service. Confirm panel access, PHP features, database administration and any Tor-accessible mail workflow before delivery.
Tor routing affects latency, so test the application with its intended audience. Review HTTPS and authentication for your design; no streaming rate or protection from every denial-of-service attack is guaranteed.
Plan files, database exports, stack compatibility and service-key custody together. Confirm how keys are delivered and restored, and what a selected backup option covers before replacing an existing service.
Understand the asset, network and confirmation journey, and protect the information that connects your project to a payment.
Read the guideDocument-free onboarding addresses one collection point. Understand the other records, access paths and payment traces around a hosted project.
Read the guidePlan a legitimate onion publication with controlled backend exposure, careful content review, service-key recovery and an explicit audience-access model.
Read the guideChoose your resources. Keep control of your identity.