Backends and APIs
The part nobody sees and everybody depends on. Data models that survive the second year, APIs with documentation that matches the code, background jobs, notifications and the admin screens that let a small team run the whole thing.
What you end up with
- A documented API your apps and partners can build against
- A Postgres schema with migrations that never lose data
- Background jobs for email, push and scheduled work
- An admin panel for support, moderation and reporting
- Automated tests that run before anything reaches production
How we do it
Tests are the specification
Milau's API ships behind more than 1,800 automated tests. Every bug becomes a test before it is fixed.
Additive changes only
A deploy never breaks the app version already on people's phones. Old clients keep working.
Kill switches
New features sit behind flags that can be turned off from the admin panel without a release.
Questions about this
Can you work with our existing database?
Yes. We read it first, write down what we find, and change it in small, reversible steps.
Node or Python?
Python by default. We will use what your team already runs if that is the better call.
Tell us what you are making.
A few lines is enough. A person reads it and writes back with what it would take.