Deployment target matrix
19 infrastructure profiles, including 5 Indian providers. Each profile identifies the persistence, compute, and operating model to assess when planning a KynetraDB environment.
Planning baseline
1. Choose a profile that supports persistent storage. 2. Define the data, backup, networking, and identity boundary. 3. Request a preview to scope an implementation plan.
All 19 target profiles
Best fit. Stateful volume, single-region, sub-second cold start.
Operating profileDisk-backed web service with blueprint.
Operating profileDockerfile auto-detect, attach a volume in the UI.
Operating profileServerless container with GCS-backed WAL volume mount.
Operating profileApp Runner for managed, ECS Fargate + EFS for production.
Operating profileBicep template with Azure Files volume.
Operating profileDoctl spec; for stateful production use DO Droplet + Block Storage.
Operating profileCloud-init script + attached volume + Docker auto-restart.
Operating profileEdge gateway Worker in front of a real origin, caches reads at 300+ POPs.
Operating profileContainer stack with heroku.yml.
Operating profileHelm chart with StatefulSet + PVC + Secret.
Operating profileTerraform: compute + block volume. Always-Free tier compatible.
Operating profileTerraform: ECS + Cloud Disk + Security Group (Mumbai default).
Operating profileStateless serverless container + stateful instance + block storage.
Operating profileIndia's largest CPU/GPU cloud. Cloud-init + block volume on KVM.
Operating profileCloud-init with auto-attach persistent disk; console-driven.
Operating profileAnsible playbook for bare-metal/VM; systemd unit.
Operating profileCloud-init drops in a kynetra.service systemd unit.
Operating profilePaste-in setup.sh for their post-install panel.
Operating profilePersistence note
Stateful data needs persistent storage, backups, access controls, and an explicit recovery plan. Treat ephemeral filesystems as unsuitable for persistent database state. The profiles above identify the operating model to validate during a preview engagement.
Provider prices, regional availability, managed-service features, and persistence options change independently. Confirm them with the provider while defining the final architecture.