Design archive — not shipped
This page describes a future or historical network, API, P2P, or deployment surface. The current product is a local alpha; there is no working network transfer, hosted server, public API/SDK, or deployable service.
Design Archive
Cloud Deployment Design Boundary
Provider choices remain hypothetical until there is a deployable Dits service.
Design, not a shipped service
The current product is a local alpha CLI and library. There is no hosted Dits service, complete repository remote, public API or SDK, managed webhook system, official server image, or supported production deployment. The items below are conditional design targets, not setup instructions or commitments.
Status
Dits does not deploy to or integrate with AWS, Google Cloud, Azure, Cloudflare, or another cloud provider as a hosted repository service. There are no supported Terraform modules, managed-service templates, data-region guarantees, or cloud cost models.
Possible design targets
- A provider-neutral application contract with a deliberately small supported infrastructure matrix.
- Encrypted service networking, scoped identities, durable state, tested backups, and explicit region behavior.
- Measured capacity and cost guidance tied to a real implementation and workload.
Prerequisites before implementation claims
- A production-capable server and remote protocol independent of cloud-provider marketing.
- Reviewed infrastructure code, release artifacts, observability, migrations, and recovery exercises.
- Legal operator, data-flow inventory, subprocessor decisions, and published support boundaries.
What can be evaluated today
- Store independently verified repository backups using your existing provider tooling.
- Do not configure speculative Dits cloud keys or endpoints from historical examples.
- Evaluate the local CLI without assuming cloud lifecycle or remote hydration behavior.