Start with a visible platform price, add only the infrastructure you use, and scope migration or managed operations separately. Subscription, usage, and human responsibility stay on distinct commercial lines.
Plans cover access to the Tabbify Cloud platform. Running resources use the published compute, storage, and transfer rates further down the page.
Understand the platform, document the workload, and decide whether a Tabbify environment fits before starting paid usage.
The core Tabbify Cloud control surface for one tenant environment. Infrastructure consumption is billed from the published usage tables below.
For teams that need migration work, a named engineer, custom operating boundaries, and commercial terms around a real application estate.
Usage billed separately. The Base subscription does not hide compute, storage, transfer, migration, or support costs inside one opaque allowance.
These commercial stages are scoped independently from the cloud subscription and usage bill.
Establish what is running, what should move, and what Tabbify will actually own before a production quote is issued.
Move one representative workload to prepared Tabbify Cloud infrastructure and prove the complete operating path.
Keep the named engineer, prepared compute, and agreed operational responsibilities after the pilot proves the model.
A small web app and a multi-service production system should not receive the same invented package price.
Shared or dedicated CPU, memory, storage, selected placement, and the maintenance expectations for the workload.
Number of APIs, web apps, workers, scheduled jobs, environments, domains, and release paths.
PostgreSQL, KV, object storage, existing providers, data volume, migration work, backup, and recovery requirements.
Current documentation, unsupported dependencies, build changes, downtime tolerance, and cutover complexity.
Coverage hours, response expectations, release frequency, incident coordination, and reporting requirements.
Tenant-private connectivity, approved public routes, custom domains, transfer volume, and any external dependencies.
Discovery, packaging, data movement, route changes, validation, and handover.
CPU compute, volumes, early-access data resources, networking, storage, and transfer.
Named engineer, coverage window, deployment coordination, runbooks, and incident route.
Application development, unsupported remediation, third-party licenses, and responsibilities kept by the customer.
Published infrastructure rates sit beside the managed engagement. They price measurable resources; migration work and operational responsibility remain separate commercial lines.
Metered by the second and shown as a 30-day month. Capacity beyond the agreed environment follows these reference rates.
| Preset | CPU | RAM | Price / mo |
|---|---|---|---|
| shared-cpu-1x | 1 shared | 256 MB | $1.16 |
| shared-cpu-1x | 1 shared | 512 MB | $1.91 |
| shared-cpu-1x | 1 shared | 1 GB | $3.42 |
| shared-cpu-1x | 1 shared | 2 GB | $6.42 |
| shared-cpu-2x | 2 shared | 1 GB | $3.83 |
| shared-cpu-2x | 2 shared | 4 GB | $12.84 |
| shared-cpu-4x | 4 shared | 1 GB | $4.67 |
| shared-cpu-4x | 4 shared | 8 GB | $25.67 |
| shared-cpu-8x | 8 shared | 2 GB | $9.33 |
| shared-cpu-8x | 8 shared | 16 GB | $51.35 |
| performance-1x | 1 dedicated | 2 GB | $18.60 |
| performance-2x | 2 dedicated | 4 GB | $37.20 |
| performance-4x | 4 dedicated | 8 GB | $74.40 |
| performance-8x | 8 dedicated | 16 GB | $148.80 |
| performance-16x | 16 dedicated | 128 GB | $585.75 |
These rows are infrastructure rates only. PostgreSQL, KV, and S3-compatible operating scope is reviewed separately and is not assigned an invented list price.
| Resource | Price | Unit |
|---|---|---|
| Additional RAM | $3.00 | per GB / month |
| Persistent volume storage | $0.09 | per GB / month |
| Volume snapshots | $0.05 | per GB / month |
| Outbound transfer — EU & North America | $0.012 | per GB |
| Outbound transfer — rest of world | $0.024 | per GB |
| Dedicated IPv4 address | $1.20 | per month |
Prices in USD, excluding VAT or sales tax. Payments are processed by Paddle.com Market Ltd, our Merchant of Record. Region availability and the final infrastructure quote are confirmed before deployment. See our Refund Policy and Terms of Service.
No production change happens before the scope, cutover contingency, acceptance checks, and responsibility matrix are agreed.