A real app is rarely just an app. It talks to a server, a database, a payment service, a notification service. If a builder wants you to move all of that into its own world, it has made the choice for you. Burrow does not.
Your backend stays yours
If you already run a backend, keep it. Burrow connects to your API, to your database, or to any service that speaks the usual ways of the web. Your data stays where you put it, under the rules you set.
If you do not have a backend yet, you choose one. Nothing in Burrow forces a particular choice, and nothing is hidden behind a Burrow account.
Built in for common services
Some services are so common that it makes sense to have them ready. Burrow is built to work with Supabase, Firebase and Stripe without you writing the plumbing: sign-in, data and payments, for example. They are trademarks of their owners, named here only to say what Burrow works with, and no partnership is implied.
Built in does not mean required. You can use all, some or none of them, and still connect to anything else.
Tested offline, in a sandbox
Testing against a live service is slow, can cost money and can hurt real data. So every service Burrow connects to is also made available as a sandbox: a pretend version that behaves like the real one and runs on your own computer, offline.
- Try a payment without moving any money.
- Try a sign-in without creating a real account.
- Make the pretend server fail on purpose, to see what the app does.
- Run the same checks again and again and get the same answer.
When you are ready, you point the app at the real service. The app’s logic does not change.
Why this matters as an app grows
As an app grows, its connections multiply. Each one is a place where the app can break for reasons outside your control. Having every connection described once, checked on every change and testable offline keeps that growth manageable.
Secrets stay yours
Services need keys and passwords to talk to them. In Burrow, those belong to you. They are not folded into the app’s design file, and they are not kept somewhere you cannot reach. You decide which key goes to which service, and who on your team may see it.
Plain words about connections
A connection in Burrow is described like everything else: short steps, in plain sentences. “When the order is placed, send it to the orders service and wait for the answer.” Anyone on the team can read that, and Burrow checks it on every change, so a service that is renamed or removed shows up as a problem right away.
What is true today
Burrow is in development. Camera, maps, payments, notifications and storage are part of the app library, which comes after the language and is being built next. The connections and sandboxes belong to the Studio, which follows. The direction is fixed; the dates are not, and we will not invent any.