Langrove vs. backend and hosting services.
They give a developer the parts. Langrove gives you the parts already joined, in your own AWS account.
| Backend and hosting servicesTypically | LangroveIn your own AWS account | |
|---|---|---|
| Where it runs | Their cloud | Your own AWS account |
| What you get | Separate parts: database, hosting, sign-in | 54 capabilities, already joined |
| Who joins them | A developer, app by app | Done once, for every app |
| Access rules | Written and kept up by hand | Checked on every request, by who is signed in |
| Going live | Anyone who can deploy | Only a person you approve. Revert in about 30 seconds. |
| IT review | One for each service | Once, for every app |
| Pricing | Per project, per service | One price per AWS account. AWS bills you directly. |
On our Hosted plan, apps run in Langrove's AWS account in Europe until you move them to yours.
Which one fits?
A backend service fits when
- You're building a public product with your own engineering team.
- You need web pages rendered on the server.
- Your developers want to pick and run each part themselves.
Langrove fits when
- You're building apps for your company, not a public product.
- You want sign-in, data and hosting decided once, for every app.
- IT wants one stack to review, in your own account.