What it does
The server has adapters for fifteen providers. Twelve of them can create a container service or a virtual machine from an image you supply; two create PostgreSQL databases; Cloudflare offers inventory and edge-gateway calls and no deploy. Credentials are sealed in the log. This is code that calls provider APIs. It is not a tested installer: one provider has an opt-in live test, no adapter attaches persistent storage, and the image has to be one you build and host.
How it works
An administrator adds a provider with POST /admin/providers: a name, a provider kind and a credential map whose fields depend on the provider, such as a token, a key pair or a service account file. The credentials are sealed with AES-256-GCM under a vault key that is separate from the token-signing secret, so rotating the signing secret does not make stored credentials unreadable. List and get calls never return them. A per-provider circuit breaker wraps the calls, and its state is readable at /admin/providers/{id}/breaker.
Each adapter implements validate, list instances, deploy, destroy and, for some providers, resize. validate calls the identity endpoint of the provider. deploy creates a resource from a request that names an image, an instance name, a region, a size, environment variables, CPU and memory. The result is the provider instance id, a status and a public URL when one exists.
What deploy creates depends on the provider. AWS creates an App Runner service, and accepts images from ECR or ECR Public and refuses others. Google Cloud creates a Cloud Run service. Azure creates a Container Apps environment and app. Fly creates an app and a machine. Railway creates a project with an image-backed service. Render creates an image-backed web service. Heroku creates a container-stack app and its configuration, and releasing the image is a manual step. DigitalOcean creates an App Platform app and also lists and destroys droplets. Linode and Vultr create a virtual machine whose start-up script runs the image. Oracle and QuantumOS have their own adapters. Supabase and Neon create PostgreSQL projects, not KynetraDB compute. Cloudflare lists Workers, Pages projects and D1 databases and manages Hyperdrive configurations.
The same adapters sit under the cluster route and the infrastructure job ledger. The command line can import a DigitalOcean credential from an environment variable with kynetra provider import-env.
Where you reach it
- HTTP
GET|POST /admin/providers, GET /admin/providers/catalog, GET|DELETE /admin/providers/:id - HTTP
POST /admin/providers/:id/test, GET /admin/providers/:id/instances, GET /admin/providers/:id/breaker - HTTP
POST /admin/providers/:id/deploy - HTTP
DELETE /admin/providers/:id/instances/:instance_id, POST /admin/providers/:id/instances/:instance_id/resize - CLI
kynetra provider import-env digitalocean --name <name> [--env VAR] [--rotate]
Example
{
"image": "registry.example.com/team/kynetradb:TAG",
"name": "kdb-demo",
"region": "ams3",
"size": "basic-xxs",
"env": {}
}Limits
- Not a tested installer. The tests that exercise deploy, list or destroy requests cover DigitalOcean (9 unit tests, most against a mock server, plus gated live tests), QuantumOS (5), Oracle (2) and Azure (1). The AWS, Google Cloud, Fly, Heroku, Railway, Render, Linode, Vultr, Neon, Supabase and Cloudflare adapters have no request-level test.
- The one live check is opt-in and needs your own token. It deploys a generic public test container to DigitalOcean App Platform, resizes it and destroys it. It does not deploy KynetraDB.
- You supply the image. The site does not document a published KynetraDB image in this edition, and AWS App Runner accepts ECR images and refuses others.
- No adapter creates or attaches a persistent volume for the data directory. Treat storage on a container service as ephemeral unless you point the instance at PostgreSQL through its environment: set KYNETRA_STORAGE_BACKEND to postgres or pg, together with KYNETRA_PG_URL. Any other value of KYNETRA_STORAGE_BACKEND is not rejected. The server logs that it is using the file log and starts on local files, so a misspelt value leaves you on ephemeral storage without an error.
- Heroku deploy creates the app and its configuration. Releasing the image is up to you.
- The Cloudflare adapter offers inventory and edge-gateway calls, with no deploy or destroy. Supabase and Neon create PostgreSQL projects.
- The deployment page lists target profiles with manifests and notes. Those are not installers either, and this entry is separate from them.
Evidence
- On this siteDeployment target matrix: target profiles, not installers
- On this siteAPI reference: admin provider routes
- TestsCovered in the engine repository by 15 catalogue and credential-vault tests, 9 DigitalOcean adapter tests (image parsing, and destroy and resize calls against a mock server), 6 gated live DigitalOcean tests (they need a token and are skipped without one), 5 QuantumOS tests, 2 Oracle tests and 1 Azure test
Test coverage is listed as present in the engine repository at this edition. This page does not report test results.
KynetraDB is in private preview
Request a preview to talk through the limits above against your own workload.