In pilot
Databases that stay where you put them.
Managed PostgreSQL, Redis and S3-compatible object storage, private by default. Connect one to a service and Dekka creates the credentials, sets the connection string and restarts the service, so nobody copies a password around.
storefront · DataExample project
orders-db
PostgreSQL 17- Address
- orders-db.production.dekka.internal
- Connects as
- DATABASE_URL
- Backups
- Daily, kept 7 days
- Public access
- Off until you open a TCP proxy
cache
Redis 8- Address
- cache.production.dekka.internal
- Connects as
- REDIS_URL
- Backups
- Not backed up
- Public access
- Off until you open a TCP proxy
uploads
Object storage- API
- S3-compatible
- Connects as
- S3_*
- Backups
- Not backed up
- Public access
- Private bucket
Managed PostgreSQLRelational databases with credentials generated for you.
Managed RedisFor caching, background jobs and short-lived data.
Object storageS3-compatible buckets that work with the SDKs you already use.
Private by defaultNo public address unless you choose to open a TCP proxy.
Connection strings, set for youDATABASE_URL, REDIS_URL or S3_* arrive in the service you connect.
Backups and restoresPostgreSQL is backed up daily and kept 7 days by default, up to 90.
MetricsConnections, memory and storage for every database.
QueuesManaged queues for work that can wait its turn.
Location you can seeEvery database and its backups, with where they live stated.
The rest of Dekka
- Managed platformApplications, workers and scheduled jobs deployed from GitHubIn pilot
- WorkspaceA canvas where every connection is real configuration, and blueprints to repeat itIn pilot
- AI GatewayOne OpenAI-compatible endpoint with rules about where prompts goIn development
- VeilGhana-aware detection and redaction of personal information, run locallyIn development
- Servers and GPUsVirtual machines and GPUs for workloads you run yourselfPlanned