Root access, and the invoice in advance.
High-performance cloud servers for when you need the operating system, not a runtime. NVMe storage, daily backups, and DDoS protection on every configuration — with the exact prorated charge shown before you provision.
- NVMe on every size
- Daily automated backups
- root access
- Preview before you pay
# what today actually costssubtotal USD 18.40tax USD 4.60credit -USD 5.00due today USD 18.00$ ssh root@acme-db-01Welcome to Ubuntu 24.04 LTS
- NVMe SSDincluded
- DDoS mitigationincluded
- Daily backupspoint-in-time
STORAGE
NVMe
High-performance SSD, every size
BACKUPS
Daily
Point-in-time recovery
ACCESS
Full root
Any package, any service
BILLING
Prorated
Previewed before provisioning
Size, price, provision
No surprise on the first invoice
Provisioning charges the project's payment method immediately, so the preview exists to make that charge something you approved rather than discovered.
- 01
Choose a size and region
Pick from the available configurations in the region closest to your users, with the price for each shown as you compare them.
- 02
See the exact charge first
A cost preview returns the prorated subtotal, estimated tax, any credit applied, and the total due today — before anything is provisioned.
- 03
Provision and take root
Start from a clean OS image or a one-click application, then install and configure whatever the workload needs.
What every server includes
The machine, and the parts around it
Storage, mitigation, and backups are part of the configuration rather than add-ons, so a server is useful the moment it exists.
Instant provisioning
Spin up servers in seconds from pre-configured images, or start from scratch with the operating system you prefer.
Seconds, not tickets
NVMe storage
Every server comes with high-performance NVMe SSD storage, so read and write throughput is not the thing holding your workload back.
On every configuration
DDoS protection
Built-in mitigation covers both volumetric floods and application-layer attacks, with nothing to configure or subscribe to separately.
Included
Automated backups
Daily backups with point-in-time recovery, so restoring to a known-good snapshot is a decision rather than a project.
Daily, restorable
One-click applications
Provision a server with common software already installed and configured, instead of running the same setup script for the tenth time.
Or a bare OS image
Full root access
Complete control of the environment. Install any package, tune any kernel parameter, run any service — this is the product for when managed is too narrow.
It is your machine
Cost preview
The number before the commitment
Ask what a configuration costs and you get the real figure for today — prorated to where you are in the billing period, with tax estimated and credit applied.
- Prorated to the day, so provisioning mid-period does not cost a full period.
- Estimated tax and any project credit are included in the total due today.
- The charge lands on the project's payment method as the server is created.
- A project with no payment method cannot provision, rather than provisioning something unpaid.
{ "subtotal": 1840, "estimatedTax": 460, "creditApplied": 500, "totalDueToday": 1800}
# then, and only then$ POST /v1/projects/:projectId/servers{ "deployed": true }
Managed or self-managed
Which product is this workload?
Both run on Cosmoner infrastructure inside the same project. The difference is how much of the machine you want to be responsible for.
Choose Cloud Hosting
- You need OS-level access or custom system packages
- You run your own database, queue, or long-lived daemon
- The software you need is not a web service built from a repo
- You want a one-click application image as a starting point
Choose Apps instead
- Your workload is a web service or static site in a repository
- You want every push to build and deploy automatically
- You would rather not patch, size, or monitor a machine
- Logs, metrics, and a live console are enough access
What it costs
Priced per size, prorated both ways
A server is billed on the size you pick, from the day you create it. Destroy it halfway through the month and the unused half comes back as credit.
- The server
- Per size
- One monthly price per size, covering its vCPU, memory, SSD, and the transfer allowance that comes with it. Nothing is metered on top.
- Removing a server
- Credited back
- Billing stops the moment you destroy it, and the unused part of the period is added to the project's credit balance.
- A stopped server
- Still billed
- Stopping keeps the disk and the IP reserved for you, so it keeps its price. Destroy the server to stop the charge and get the unused days back.
Each size lists its monthly price next to its vCPU, memory, and disk in the create flow, with the prorated amount due today shown before you confirm.
One project
What it plugs into
A server does not have to be an island. The domain pointing at it, the bucket it writes to, and its configuration all live in the same project.
Questions worth answering up front
Sizes, regions, one-click images, and the provisioning API are covered in the docs.
- When should I pick this over Apps?
- When you need the operating system itself: a background daemon, a database you run yourself, custom system packages, or kernel-level configuration. If your workload is a web service built from a repository, Apps is less to operate.
- How do I know what it will cost?
- Ask for a preview before provisioning. It returns the prorated subtotal, the estimated tax, any credit on the project, and the total charged today — so the first invoice holds no surprises.
- When am I charged?
- The prorated amount is charged to the project's payment method as the server is provisioned. A project with no card on file cannot provision — the request is refused rather than creating a server that is not paid for.
- Which sizes and regions can I choose?
- The available configurations and regions are queried live rather than published as a fixed list, so what you see in the control panel is what can actually be provisioned right now, with current pricing.
- Can I use my own domain?
- Yes. Manage the domain in the same project and point its A or AAAA record at the server, without a second DNS account in the loop.
- Does it share billing with the rest of the project?
- Yes — servers appear on the project's subscription alongside its apps, buckets, and domains, on one payment method and one invoice.
On one invoice
Servers bill like everything else
A server joins the project's subscription rather than starting a separate relationship with a separate card and a separate renewal date.
One payment method
The project's card pays for its servers, apps, buckets, and domains together.
Prorated from day one
You pay for the part of the period you actually used, not the whole of it.
No card, no charge
Provisioning is refused outright when a project has no payment method on file.