Custom development
Custom backend and API development
We build the server side behind your website, mobile app or partner integrations: business logic, data storage, sign-in and performance under load. If outside developers need your data, we design an API for them and document it.
Scope
What's included
- Data model: entities and relationships, designed before code.
- API contract (REST or GraphQL), agreed before development, so front-end teams and partners don't wait.
- Business logic, sign-in and roles.
- Integrations, queues and webhooks for background jobs.
- API documentation, automated tests and monitoring. Another team can pick up the system later.
Price
How we price it
The number of entities, the complexity of the business rules and the number of integrations. Security requirements and expected load matter too. We design the data model and API contract first, and that shows the real scope.
Process
How we work
We model the data around your scenarios and show you the schema before writing code. Then we agree the API contract, so other teams can start in parallel. We write the logic, integrations and tests, with security built in from the start. At the end we set up monitoring and show the system working on real data.
Our work
Proof
Backend for a meet-up app
(client unnamed). NestJS and PostGIS. It handles a map with geolocation, an invitation feed, real-time chat and check-in confirmation by location. All 11 modules from the specification are done.
Short-term rental marketplace
(client unnamed). The app is covered by 227 automated tests.
TruckFuel
Each fuel network connects to the server through its own module. Adding a network doesn't touch the rest of the system.
Questions
FAQ
Can you build an API for our existing app or site?
Yes, including a public API for partners, with documentation and versioning.
How do you handle security?
Sign-in, roles, input validation, rate limiting and an audit log are part of the architecture from day one.
Do you write tests?
Yes. Automated tests stop the next change from breaking working logic.
REST or GraphQL?
REST is simpler for standard integrations and partner APIs. GraphQL suits several apps that each need a different slice of the same data. We decide when designing the contract.
Get in touch
Tell us what you need built
We'll reply within one business day with a few questions about the task. Then a call and a free estimate for the first stage.