Choosing a platform · By Rivtor · Updated
Calculate hosting costs for a small full-stack SaaS
A useful hosting estimate includes the whole application: frontend, API, database, workers, storage and bandwidth. Compare equivalent resource and operational requirements on the same billing interval.
Compare Rivtor plans for your workload →
Define the workload first
List services, memory, database size, expected traffic and processes that must remain running. Include staging only when you need it. A static portfolio and a paid SaaS with continuous background jobs are different workloads even when both are described as a web app.
Separate included and metered resources
A minimum subscription does not necessarily pay for every service. Check included usage, separate resource charges and what happens when a limit is reached. Annual pricing involves an annual commitment and should not be presented as identical to buying a single month.
Include operational requirements
Account for backups, recovery checks, domains and an appropriate data region. A cheaper setup without required availability or recovery characteristics is not an equivalent configuration. Measure a representative workload before extrapolating future costs.
Use current Rivtor plan details
The pricing page provides Rivtor amounts, included resources and commercial-use limits. Choose the smallest plan that fits the workload. A trial entitlement is temporary; neither it nor a low-traffic example establishes unlimited permanent production capacity.
Use an explicit worksheet
| Component | Questions to answer |
|---|---|
| Frontend | Static or server-rendered? How much memory and traffic? |
| API | Continuous service, concurrency and request duration? |
| Postgres | Stored data, connections, backups and recovery needs? |
| Worker and Redis | Always running, queued workload and retry behavior? |
| Storage and bandwidth | Retained uploads, downloads and billable transfer? |
| Operations | Monitoring, regional needs and support requirements? |
List the resources before inserting vendor prices. A worker and database cannot be assumed to be included simply because an advertised application instance has a low starting price.
Compare the same operating conditions
Use the same month length, currency, region and application workload. Separate recurring plan fees, included usage credits, resource charges and optional additions. Record the date of each official pricing source and avoid treating different memory or recovery allowances as equivalent.
Calculate a normal month and a busier month. For usage-based offerings, identify which activity increases cost; for fixed allocations, identify what happens when the allowance is reached. Include project count and additional services in the estimate.
Choose a plan based on the application
Rivtor's pricing and limits define current resources and commercial-use conditions. Use those shared definitions for a decision rather than assuming a free development project can run a commercial service indefinitely.
Compare Rivtor and Railway, Render, or Vercel with Supabase for workflow differences. Source pricing: Railway, Render, Vercel, and Supabase.
Next steps
Read the Rivtor reference for supported configuration and limitations, and use the deployment quickstart when trying Rivtor for the first time. Validate workflows with synthetic data before connecting valuable production records.