Platform
A 9live environment is a set of services, your application processes and managed databases, running on dedicated hardware in Mumbai and connected by a private network. This page describes what the platform does and where its limits are.
Compute
Resources are reserved for your environment for as long as the plan is active.
- Dedicated vCPU
- One vCPU per physical CPU thread, no oversubscription.
- 8 / 12 / 16
- Memory
- Reserved, not overcommitted. The full amount is available to your processes and databases.
- 16 / 32 / 48 GB
- Process types
- Run web servers, background workers and scheduled jobs side by side, with CPU and memory set per process.
- Isolation
- KVM-based microVMs, one per customer environment.
- Changing plans
- Moving to a larger plan needs a short restart, scheduled at a time that suits you.
Deploys
Connect a GitHub repository and pick a branch. We detect the framework or use your Dockerfile, and build on every push.
Each release runs your release command, passes a health check, and only then receives traffic.
# 9live.toml
[app]
name = "acme-api"
region = "mumbai"
plan = "grow"
[build]
command = "npm ci && npm run build"
[deploy]
release = "npx prisma migrate deploy"
health = "/healthz"
[processes]
web = { command = "npm start", cpu = 4, memory = "8GB" }
worker = { command = "node dist/worker.js", cpu = 2, memory = "4GB" }
[[databases]]
engine = "postgres"
version = "17"
[[databases]]
engine = "redis"$ git push origin main
Build a1f3c2e main
Detected Node.js 22, npm
npm ci 19.4s
npm run build 38.1s
Image pushed 3.2s
Release npx prisma migrate deploy
2 migrations applied
Health GET /healthz 200 OK (3/3)
Traffic switched to a1f3c2e
previous release b72e019 kept for rollback- Dockerfile or automatic detection with Cloud Native Buildpacks
- Release commands for database migrations
- Health checks before traffic moves; failed releases never receive traffic
- Previous releases kept for one-step rollback
- Staging environment with its own database on Grow and Scale
- A CLI and an API for everything the dashboard does
Databases
Each plan includes a number of managed database instances. Mix engines as needed.
- Managed PostgreSQL
- A dedicated PostgreSQL instance on local NVMe, configured for your plan's memory and storage.
- PostgreSQL 16 and 17
- Managed MongoDB
- MongoDB Community Server on dedicated NVMe, run as a three-member replica set on Grow and above.
- MongoDB 7 and 8
- Managed Redis
- A dedicated Redis instance on your environment's private network, for caching, sessions, rate limiting, pub/sub and job queues.
- Redis 7.4
Networking
- Private network
- Application processes and databases communicate over a private network. Databases have no public address unless you add an allow list.
- Domains and TLS
- Custom domains with certificates issued and renewed automatically. TLS 1.2 and 1.3.
- Edge
- HTTP/2, compression and caching for static assets, served from Mumbai.
- DDoS filtering
- Volumetric DDoS filtering upstream of our network edge.
Monitoring and logs
- Logs
- Build, application and database logs, searchable in the dashboard and streamable from the CLI.
- Kept 14 days
- Metrics
- CPU, memory, disk, request latency and error rate per process, and database-specific metrics.
- Alerts
- Threshold alerts by email, Slack or WhatsApp.
- Grow and Scale
- Status page
- Platform incidents and maintenance are posted on our public status page.
Access and security
- Team roles
- Owner, admin, developer and read-only roles, per environment.
- Two-factor authentication
- Required for account owners, available to all users.
- Single sign-on
- SAML or OIDC.
- Custom plans
- Audit log
- Deploys, configuration changes and access grants, with the user and time of each.
- Shell access
- SSH into your own environment for debugging.
Frameworks
- Next.js
- TypeScript
- Node.js
- JavaScript and TypeScript
- NestJS
- TypeScript
- FastAPI
- Python
- Django
- Python
- Laravel
- PHP
- Spring Boot
- Java and Kotlin
- Ruby on Rails
- Ruby
- Go
- Go
Current limitations
What 9live doesn't do today, so you can decide early whether it fits.
- One primary region, Mumbai. Singapore and Frankfurt are available only on Custom plans.
- No automatic horizontal scaling across hosts. Scaling is vertical within a plan, or by adding plans.
- No managed MySQL yet. MySQL schemas can be converted to PostgreSQL during migration.
- No GPU instances on standard plans.
- No free tier.
Talk to an engineer about your setup
Tell us what you run today and where it runs. We reply within one business day with a recommended plan and an estimate for the migration.