How it works
The architecture behind OneBit Deploy — builds, container images and Kubernetes.
Understanding what happens under the hood helps you reason about builds, deploys and limits.
Build → image → run
When you deploy, OneBit:
- Pulls your source from GitHub (or your uploaded ZIP).
- Builds it into a container image — a self-contained, runnable artifact.
- Pushes the image to an internal registry.
- Runs the image on a managed Kubernetes cluster.
- Exposes it on a public URL through the platform's edge router, with automatic SSL.
Because each deploy is a versioned image, deployments are repeatable and isolated from each other.
Where it runs
OneBit Deploy runs on a managed Kubernetes platform across European data centres, operated by a Nigerian company and billed in naira. You cannot choose where an app runs — region selection is not a feature yet.
Routing and the edge
Incoming requests hit the platform's edge router, which terminates TLS and routes each request to the right app based on its domain. You can shape this behaviour with request rules.
Resources and scheduling
Apps are scheduled onto the cluster within the limits of your plan. Free-plan apps sleep when idle; Starter and above stay running. See Plans & quotas for the limits.