Shared Compute - General Compute
$5.00/mo
1 vCPU · 1 GB · 20 GB
Choose location
Ashburn, United States
| Provider | Plan | vCPU | RAM | Disk | Regions | Billing | Price |
|---|---|---|---|---|---|---|---|
| Enzonix | Shared Compute - General Compute | 1 | 1 GB | 20 GB | Ashburn, United States | Fixed price | $5.00/mo |
| Enzonix | Shared Compute - General Compute | 1 | 1 GB | 20 GB | Amsterdam, Netherlands | Fixed price | $5.00/mo |
| Enzonix | Shared Compute - General Compute | 2 | 4 GB | 80 GB | Amsterdam, Netherlands | Fixed price | $9.00/mo |
| Enzonix | Shared Compute - General Compute | 2 | 4 GB | 80 GB | Ashburn, United States | Fixed price | $9.00/mo |
| Enzonix | Shared Compute - General Compute | 4 | 8 GB | 160 GB | Amsterdam, Netherlands | Fixed price | $16.00/mo |
| Enzonix | Shared Compute - General Compute | 4 | 8 GB | 160 GB | Ashburn, United States | Fixed price | $16.00/mo |
| Enzonix | Shared Compute - General Compute | 8 | 16 GB | 320 GB | Amsterdam, Netherlands | Fixed price | $32.00/mo |
| Enzonix | Shared Compute - General Compute | 8 | 16 GB | 320 GB | Ashburn, United States | Fixed price | $32.00/mo |
| Enzonix | Shared Compute - General Compute | 1 | 1 GB | 20 GB | Ashburn, United States | Hourly | $0.007/hr |
| Enzonix | Shared Compute - General Compute | 1 | 2 GB | 40 GB | Ashburn, United States | Hourly | $0.01/hr |
| Enzonix | Shared Compute - General Compute | 2 | 4 GB | 80 GB | Ashburn, United States | Hourly | $0.015/hr |
Cal.com Instant App
Cal.com is open-source scheduling for event types, availability and booking links. Compare live VPS prices, CPU, RAM, disk and regions, launch with a prepared admin account on the plan you choose, and keep root access so calendars stay on your server.
Cal.com
Instant App on marketplace VPS
Live marketplace offers
Choose billing and size, compare providers side by side, pick a location, then launch.
1 provider
Cal.com is self-hosted scheduling for event types, availability windows and public booking links. Use it instead of paying for Calendly. Sign in as admin after boot, connect calendars when you want, and keep bookings on your disk. No Instant App form fields are required at create time.

Sign in with the prepared admin email and password. Public signup stays closed by default.

Create meeting lengths and booking pages your guests can open without an account.

Set weekly hours and buffers so bookings land only when you are free.

Manage profile, security and integrations from the admin settings after first login.
Compare live Cal.com VPS plans from independent providers, then self-host scheduling and booking pages on the offer you pick. Use it instead of paying for Calendly.
See live prices, regions and plan sizes before you buy. Shop self-hosted scheduling hosts across independent providers, starting around 4 GB RAM.
Pick a plan and Cal.com is prepared on that VPS for you, including Postgres, Redis and the first admin account. You still get root access.
Compatible offers list cities and countries. Keep latency low for the team that owns availability and the people who book.
Cal.com Instant App creates the first admin on boot and leaves public signup off. Strangers cannot open your scheduling console without those credentials.
Most Cal.com or self-hosted scheduling VPS pages sell one company's servers. NodeRings lists Compute Instance plans from independent providers so you can compare offers by price, size and region, then launch on the one that fits.
Cal.com Instant App prepares Cal.com on the provider VPS you selected. NodeRings does not operate that hardware or sell its own VPS fleet.
Compare plans, pick a provider offer, and launch Cal.com on that server.
01
Browse live offers below. Plan for about 2 vCPU, 4 GB RAM and 40 GB disk as a starting point. Sort by provider, size, price and region.
02
Finish checkout on that provider offer. Cal.com, Postgres, Redis and the first admin account are prepared on the VPS for you.
03
Open the site URL, sign in with calcom_admin_email and calcom_admin_password from your server notes, then publish a booking link.
NodeRings Instant App brings Cal.com up with Docker Compose and creates the first admin. Use the sections below to reach the UI, find passwords, and operate the stack.
Credentials are written on first boot to:
/root/.noderings_passwordRead them over SSH:
cat /root/.noderings_passwordCompose project directory
/opt/noderings/calcom
/opt/noderings/calcom/docker-compose.yml
/opt/noderings/calcom/.envWorking directory for compose and secrets.
Data mounts
/opt/noderings/calcom/pgdata
/opt/noderings/calcom/redisdataPostgres and Redis volumes.
Credentials file
/root/.noderings_passwordWritten once on first boot.
Install logs
/tmp/calcom-admin.logSetup API verification log from first boot.
Boot unit
/etc/systemd/system/noderings-calcom.serviceBrings compose up after Docker is ready.
Compose runs Cal.com with Postgres 16 and Redis 7. The UI is on HTTP port 80 (container 3000).
calcomCal.com web UI and API.
databasePostgres 16 for users, event types and bookings.
redisRedis for caching and background jobs.
Container status
cd /opt/noderings/calcom && docker compose psLive logs
cd /opt/noderings/calcom && docker compose logs -fRestart containers
cd /opt/noderings/calcom && docker compose restartsystemd unit status
systemctl status noderings-calcomYour Cal.com instance starts on http://. Cloudflare can give visitors a padlock without installing anything on the VPS.
Add your domain
Sign up at Cloudflare and add the domain you want to use.
Point it at your VPS
Create an A record to your server IP and leave the orange cloud on.
Open the https site
Visit https://your-domain/ and sign in with the admin credentials from your server notes.
Only allow Cloudflare
Optional. With SSH (port 22) already allowed and everything else blocked by default, open only Cloudflare to ports 80 and 443:
curl -s https://www.cloudflare.com/ips-v4 | while read ip; do sudo ufw allow from "$ip" to any port 80,443 proto tcp; doneKeep port 22 allowed for SSH. Leave other ports denied except this Cloudflare allow for 80 and 443.
Cal.com is a Next.js app with Postgres and Redis. Give it enough RAM for first boot migrations and steady booking traffic.
| Workload | Illustrative starting point | Note |
|---|---|---|
| Solo scheduler | 2 vCPU / 4 GB RAM / 40 GB disk | Suggested Instant App floor for admin UI and light booking volume. |
| Small team calendars | 2 vCPU / 8 GB RAM | More headroom when several event types and calendar syncs run together. |
| Integrations and webhooks | Same size; watch outbound APIs | OAuth calendar apps and payment plugins need your own API keys. |
| Public internet exposure | Same size; add TLS | Admin login helps. Prefer TLS before you share booking links widely. |
These are starting points, not guarantees. Needs depend on booking volume, calendar sync and concurrent users.
This is self-hosted Cal.com on a provider VPS, not managed Calendly. You pick the plan. Cal.com is prepared on that server. Day-to-day care stays with you.
Cal.com is prepared on the VPS with Postgres and Redis, no Instant App form variables, and a first admin account created on first boot.
Root SSH on the VPS. You own provider billing, DNS, TLS, firewall choices, changing the admin password, calendar OAuth keys, backups and keeping Cal.com updated.
Managed Cal.com SaaS, Calendly seats, guaranteed uptime or backups beyond what the provider offer states, and hosting your calendars on NodeRings infrastructure are not bundled in.
NodeRings helps with marketplace, billing and console. Provider hardware issues go to that provider. Looking after Cal.com on the server is yours.
No. You get a virtual machine with Cal.com prepared for you, plus root access. That is different from Calendly SaaS or a managed care plan that owns updates for you.
It prepares Cal.com on the VPS you choose so you skip hunting through install guides by hand. It is still your self-hosted server, not a separate managed hosting brand.
Open http://YOUR_IP/ and sign in with calcom_admin_email and calcom_admin_password from /root/.noderings_password.
No. Public signup stays disabled by default. Invite or create users from the admin UI when you want them.
A common starting point is about 2 vCPU, 4 GB RAM and 40 GB disk. Add RAM when calendar sync and booking traffic grow.
You confirm the plan and finish checkout. When the server is ready, open the site URL and sign in with the admin credentials from your server notes.
Yes. Each compatible plan lists available regions. Pick the city or country that matches latency and compliance needs.