We handle
- Running, restarting, and scheduling the container
- Database provisioning, credentials, patching, and backup
- TLS, routing, and the private network between the two
- Base platform patching and capacity
Entry
Application Starter
One application container and one managed database, wired together.
What this tier is
This is the smallest useful shape for a real application: something that runs your code and something that keeps your data, on separate lifecycles, talking over a private network. Your container can be restarted, rebuilt, or rolled back without any risk to the database.
Bring a container image or a repository with a Dockerfile. We run it, put it behind the edge with a certificate, inject the database credentials as environment variables, and keep both halves patched.
Specification
| Compute | 1 container, 1 vCPU equivalent burst |
|---|---|
| Memory | 1 GB application memory |
| Storage | 10 GB persistent volume |
| Database | Managed MariaDB or PostgreSQL, 5 GB |
| Networking | Private in-cluster DNS to the data tier |
| Public access | One hostname with managed TLS |
| Backups | Daily database dump, 14-day retention |
| Deploy | Container image or repository with a Dockerfile |
What is included
- One application container from your image or Dockerfile
- Managed MariaDB or PostgreSQL schema with dedicated credentials
- Private in-cluster address for the database; not exposed to the internet
- Environment variables and secrets injected at runtime, not baked into images
- Public hostname with managed TLS
- Daily logical database backup, fourteen-day retention
- Container logs retained and readable on request
Typical use cases
- An internal tool or admin panel used by a handful of people
- A side project that has become load-bearing for a business
- An API backing a mobile or single-page application
- A prototype that needs a real URL and real persistence to be evaluated
Responsibility split
Written down so there is no argument about it later.
You handle
- Your application code and its container image
- Schema migrations and application-level data integrity
- Deciding when to scale up to the production tier
How provisioning works
Operator-provisioned. We need your image reference or repository and the port your application listens on. First deploy is normally same or next business day.
Order
Other tiers in Applications and databases
Redundant application instances, a larger database, and a change process.
$59 /mo
- Multiple replicas behind health checks with rolling deploys
- Larger managed database with point-in-time restore requests
- Staging environment matching production configuration
View details
A dedicated schema on our data tier, backed up and patched by us.
$8 /mo
- Dedicated schema and credentials, not a shared database
- Daily logical backup with a fourteen-day restore window
- Engine patching coordinated with you in advance
View details
A PostgreSQL database with extensions, backups, and an operator.
$10 /mo
- Dedicated database and role with least-privilege grants
- Common extensions available on request
- Daily backup with a fourteen-day restore window
View details
A Redis-compatible cache with an eviction policy you chose on purpose.
$6 /mo
- Dedicated instance, not a shared keyspace
- Eviction policy and memory ceiling agreed at provisioning
- Private in-cluster access, never exposed publicly
View details