A backend for your mobile app — from MVP to a million users
API, database, media storage and push infrastructure — on one platform. Start with a single server at ≈$8.11/mo and grow to a Kubernetes cluster with no migration to another cloud.
Sound familiar?
The technical pains of a mobile backend — and how OneCloudPlanet infrastructure removes them.
-
"A store feature took the backend down"
Traffic grew 20× in an hour, and there's one server. Autoscaling in Kubernetes adds nodes for the peak and drops them after.
-
"The Firebase bill became unpredictable"
As MAU grows, the BaaS fee grows nonlinearly. Your own backend on a VPS gives a predictable bill: fixed resources + storage at $0.0013/GB.
-
"User media bloated the server disk"
Photos and video should live not on the API server's disk but in Object Storage: cheaper, scales endlessly, served directly over HTTPS.
-
"Users complain the app is slow"
If the audience is in Ukraine/EU and the server is in the US — that's +150 ms to every request. Locations in Ukraine/Poland/Netherlands put the API next to your users.
The growth path
Not just a product list, but a story from MVP to large MAU — on the same account and network.
-
Stage 1. MVP
a single Cloud Instance
For: first users, idea validation
Configuration: ocp-1 (1 vCPU / 2 GB) to validate the idea or ocp-3 (2 vCPU / 8 GB) with headroom — API + DB on one server + a bucket in Object Storage for media.
Price: from ≈$8.11/mo (ocp-1) · comfortable ≈$20.45/mo (ocp-3)
Create a server -
Stage 2. Growth
we split the services
For: thousands of active users, first peak loads
Configuration: separate instances for API and DB (2× ocp-3), a free Load Balancer, a public IP $3/mo, a private network (VPC) between servers, Firewall — also free.
Price: ≈$43.90/mo
-
Stage 3. Production
Managed Kubernetes
For: large MAU, uneven traffic, a team with CI/CD
Configuration: a cluster with worker-node autoscaling (1 control + 3 worker ocp-3), a free LB for the API gateway, deploy through your CI.
Price: the K8s service — $0, from ≈$81.80/mo for nodes
More about Managed Kubernetes
Typical architecture
All components are in one private network (VPC), with only the load balancer exposed to the outside.
-
Mobile app iOS / Android
-
Load Balancer — free
-
API servers: Cloud Instance or K8s pods
-
Database: PostgreSQL / MySQL on NVMe
-
Object Storage (S3): photos, video, static
-
Backups + a geo-copy in another location
Your backend sends push notifications via APNs and FCM — no special infrastructure requirements, just stable outbound traffic.
Why OneCloudPlanet for a mobile backend
Predictable cost, low latency and a path to Kubernetes — on one account.
-
A predictable bill
Unlike BaaS and hyperscalers: fixed resource prices, storage at $0.0013/GB/mo, Load Balancer and Firewall — $0.
-
Latency for your users
Locations in Ukraine and the EU — the API next to your audience, less latency on every request.
-
S3 API for media
SDKs for Swift, Kotlin and React Native work with our Object Storage unchanged — presigned URLs for uploads straight from the phone.
-
A path to Kubernetes with no cloud change
When you grow — the same account, the same network, the same storage. Migration with no platform change.
-
API and IaC
Infrastructure as code (REST API + a Terraform provider), a staging environment for pennies.
-
A Firebase alternative out of the box
A Supabase (self-hosted) image from the Marketplace: auth, a realtime DB and storage on your server, with a predictable bill.
Frequently asked questions
Calculate the cost in the calculatorDeploy a backend today
A server for your API — in minutes. Hourly billing: validating an idea costs pennies.
Latest publications
Everything you need to create a stable, secure and scalable environment
Cloud on-call handover checklist for reliable 24/7 support: prevent context gaps and speed up issue resolution
A practical cloud on-call handover checklist to keep support continuity, avoid missed alerts, and resolve incidents faster across shifts.
Cloud change freeze and rollback plan for safer production releases: reduce outage risk during critical updates
A practical change freeze and rollback framework to protect production stability, keep customer services available, and recover fast if an update fails.
Cloud maintenance window planning playbook for stable service updates: reduce disruption and keep customers productive
A practical cloud maintenance window playbook to plan updates safely, reduce disruption risk, and keep customer operations predictable.
Cloud instance disaster recovery testing playbook: prove restore readiness before real outages
A practical cloud disaster recovery testing playbook to validate restore readiness, reduce recovery risk, and keep customer services available during critical disruptions.
Cloud incident response runbook for faster service recovery: reduce downtime and protect customer experience
A practical cloud incident response runbook to reduce downtime, speed up service recovery, and keep customer operations stable during disruptions.
Cloud instance capacity planning calendar for predictable growth: keep services fast during peak demand
A practical monthly capacity planning calendar for cloud instance workloads to keep response times stable during peak demand and control infrastructure spending.
Cloud instance rightsizing and cost control playbook: keep performance stable while reducing monthly spend
A practical cloud instance rightsizing playbook to reduce monthly infrastructure spend while maintaining stable service performance.
OpenStack + Kubernetes multi-region failover checklist for stable client services
Practical multi-region failover checklist for OpenStack and Kubernetes to keep client-facing services stable during outages.
OpenStack + Kubernetes multi-region failover checklist for stable client services
Practical multi-region failover checklist for OpenStack and Kubernetes to keep client-facing services stable during outages.
Cloud instance monitoring and alerting baseline: prevent silent failures before they impact customers
A practical monitoring and alerting baseline for cloud instances to detect failures earlier, reduce downtime, and protect customer experience.