No servers. No stress. Just ship.
Connect your repo. Magic Apps builds it, installs everything and wires it all up, then scales it on its own.
Your code is ready. Now what?Servers? Certificates? Scaling at 3 a.m.?Nope.
Deploy. Connect your repo. We read it, build it and put it live.Scale. Pick your regions. Copies are added when traffic climbs, and removed when it falls.Monitor. Requests, response times and logs, as they happen.
What you no longer have to do.
Set anything up
Every app comes with the pieces you would otherwise wire together yourself.
Guess where your users are
Pick your regions and your app runs right next to the people using it.
Watch the traffic
Magic Apps scales out with more instances and scales up within each one, all on its own. When the spike passes, it comes right back down.
Pay for idle machines
You only pay for what you use. A quiet week is a tiny bill; go viral and it grows with you.
Pay for what it used. Nothing else.
Compute and memory are charged by the hour for what your app used, and data by the gigabyte sent out.
Magic Apps
- Compute$0.025 per CPU, per hour
- Memory$0.01 per GB, per hour
- Data sent out$0.05 per GB
An API that averages a quarter of a CPU and 512 MB, all month
Questions
What do I need to start?
A repo. Connect it and Magic Apps works out how to build and run it.
What happens when traffic spikes?
More instances are added, and each can grow to 8 cores and 32 GB of RAM. When traffic falls, they are removed again.
What am I billed for?
The compute and memory your app used, by the hour, and the data it sent out. There is no charge per app or per seat.
