Calculator
What would your stack cost?
Pick what you run. The calculator counts the standard units and storage blocks it needs and prices them from today's public price list.
Choose your stack
Start from a stack
Your stack
1 entry- Included
Tools
500m CPU · 512 MiB
Managed sites
WordPress
The site your visitors land on
500m CPU · 1 GiB
Brings MariaDB ×1 · stack after: 1,300m CPU · 2.3 GiB · 10 GiB storage
Moodle
Courses, quizzes and enrolments, with its cron
700m CPU · 1.3 GiB
Brings MariaDB ×1 · stack after: 1,500m CPU · 2.5 GiB · 10 GiB storage
Your own code
Static site
Files served as they are
250m CPU · 256 MiB
PHP site
Apache or php-fpm serving your tree
500m CPU · 512 MiB
Laravel
PHP app built with Composer
500m CPU · 512 MiB
Node.js
A Node process and its build
500m CPU · 512 MiB
Python
A WSGI or ASGI app built with pip
500m CPU · 512 MiB
Ruby
A Rails or Rack app built with Bundler
500m CPU · 512 MiB
Go
A compiled Go service
500m CPU · 512 MiB
Rust
A compiled Rust service
500m CPU · 512 MiB
.NET
An ASP.NET Core app
500m CPU · 512 MiB
Container image
An image you publish
500m CPU · 512 MiB
Database engines
MariaDB
Smallest engine floor
300m CPU · 768 MiB · 10 GiB storage
MySQL
Same server share as PostgreSQL, plus its Router
900m CPU · 896 MiB · 10 GiB storage
PostgreSQL
Its own engine, with a WAL archiver
900m CPU · 896 MiB · 10 GiB storage
Cache
Valkey
Redis-compatible cache
300m CPU · 256 MiB
Curated components
Infisical
Secret manager, on PostgreSQL and the cache
500m CPU · 1 GiB
Brings PostgreSQL ×1 and Valkey ×1 · stack after: 2,200m CPU · 2.6 GiB · 10 GiB storage
Supabase Auth
Sign-up, sign-in and tokens on PostgreSQL
500m CPU · 768 MiB
Brings PostgreSQL ×1 · stack after: 1,900m CPU · 2.1 GiB · 10 GiB storage
Supabase REST
A REST API over your PostgreSQL schemas
500m CPU · 768 MiB
Brings PostgreSQL ×1 · stack after: 1,900m CPU · 2.1 GiB · 10 GiB storage
Add-ons
Stack needs 500m CPU · 512 MiB