Why Simplifyd
Built for African teams shipping to African users. No infrastructure to babysit. No data charges to explain. Just your app, live — and free for the people who open it.
How it works
No cluster to provision, no YAML to write. You bring a container image; Simplifyd runs it, routes to it, and meters it — all from your terminal.
One binary, edge. Log in once; the CLI remembers your workspace, project and environment.
Build your container however you already do, then push it to your workspace’s private registry. The CLI fetches push credentials for you — no docker login.
Point a service at the image and bring it up. The per-second meter starts when the container does, and stops when you take it down.
Data services
Databases, caches, queues and buckets — fully managed, billed by the second, and reachable from any service in your project over its private network.
Production-grade Postgres clusters. Automated backups, point-in-time recovery, replicas, and a connection string — all in one CLI command.
Drop-in replacement for S3. Point your existing AWS SDK at our endpoint and keep shipping — uploads, static assets, backups, archives, all in one place.
Also managed for you
edge service create --type redisedge service create --type kafkaedge service create --type static_siteedge service ingress addThe platform
Deploying once is easy. Running the same service for a year — through config changes, new team members, a bad release at 2am — is the part that decides whether a platform was worth it.
Structure
Shipping
Running it
Two-factor authentication on every account · secrets encrypted at rest with a per-project key · data stores private by default
Zerodata
Traffic to/from your app to subscribers on partner networks is delivered without deducting from their mobile data plan. It’s called datafree. It’s how you win in markets where data is a barrier to use.