Backend app development: the server side your app depends on
Backend app development is the part of an app nobody sees and everybody depends on: the API the app talks to, accounts and sign-in, the data, sync, notifications, subscription checks and the connections to your other systems. We build backends for new and existing mobile and web apps, designed to the app stores' account rules and the GDPR, hosted in an EU region in your company's account, with the code yours from the first commit.
- You see the result before it goes live
- Fixed price for the agreed scope, in writing before work starts
- Source code, domain and accounts in your company's name
What a backend does for an app
The app on the device shows things and takes input. Everything that has to be shared, checked, kept or connected happens on the backend:
| Part | What it covers |
|---|---|
| API | The interface the app uses, with versioning so older app versions keep working after an update |
| Accounts and sign-in | Email, Sign in with Apple, Google and company single sign-on, multi-factor authentication, sessions and account deletion |
| Data | The database, its structure, permissions on every record, backups that are restored in tests |
| Sync and offline | Changes made offline sent when the device is back online, with rules for conflicts |
| Notifications | Push through Apple's and Google's services, email and text, triggered by events and user settings |
| Files and media | Uploads, images and video, resized and served quickly, with access control |
| Purchases and subscriptions | Server-side verification of App Store and Google Play purchases, renewal and refund events, web payments |
| Admin and support | An internal console to help users, change settings and see what happened, without database access |
| Integrations and jobs | Connections to your CRM, ERP or other systems, scheduled jobs and queues |
Each part goes into the written scope with what the first version includes, so a quote for "the backend" can be compared line by line.
Custom backend, backend-as-a-service, or both
A backend does not have to be written from scratch. Backend-as-a-service platforms such as Firebase and Supabase provide sign-in, a database, storage and functions as a managed service, and get a first version running quickly. A custom backend, a service we write and run in your cloud account, gives full control over the data model, business rules, hosting region and costs as usage grows; we often write it in TypeScript, as our Node.js app development page describes. The choice depends on the app:
| Approach | Fits when | Watch out for |
|---|---|---|
| Backend-as-a-service | A new product, simple data, a small team, speed matters most | Data model and rules shaped by the platform; costs and limits at scale; region options |
| Custom backend | Complex business rules, integrations, strict data location, many users | More to build and run; needs monitoring and maintenance from day one |
| Combination | Managed sign-in, storage or push, with custom services for the core logic | Two sets of tools to understand; a clear line between them |
For the data itself, we usually choose PostgreSQL. It is also the most common choice in the industry: in the Stack Overflow survey 2026 (read 11 November 2026), 57.9% of those who answered the database question said they used it, ahead of SQLite at 42.1% and MySQL at 35.1%. PostgreSQL also runs on every major cloud and in Supabase, so the choice keeps options open.
Store rules that land on the backend
Several App Store and Google Play rules look like app features but are really backend work:
- Account deletion. Apple's App Review Guidelines (last updated 16 October 2026, read 11 November 2026) state in 5.1.1(v) that an app that supports account creation must also offer account deletion within the app. Google Play's account deletion requirements (read 11 November 2026) ask for an in-app path to delete the account and associated data, and a web link where users can request it. The backend has to delete or anonymise the user across the database, file storage, analytics, email tools and every connected system, and log that it did.
- Login options. Guideline 4.8 requires an app that uses a third-party or social login for the primary account to also offer an equivalent login service that limits data collection to name and email, lets users keep their email private and does not collect interactions for advertising without consent. Sign in with Apple is the usual answer, and the backend must handle its private relay email addresses.
- Purchases. Subscriptions bought in the stores should be verified and tracked on the server from the stores' own notifications, so access follows renewals, refunds and cancellations, not what the app reports about itself.
Security that starts at the API
An app's API is public: anyone can read the traffic from their own phone and send requests of their own. The OWASP API Security Top 10, 2023 edition (read 11 November 2026) puts broken object level authorisation first: an API that does not check whether the user may access the specific record requested, so changing an identifier reaches someone else's data. We check permissions on every record in one shared layer, never only in the app, and automated tests try to read and change other users' data on every endpoint before each release. Sign-in uses short-lived tokens with refresh, secrets stay on the server, rates are limited, and every administrative action is logged.
Push notifications deserve a note of their own: their content passes through Apple's and Google's servers to reach the device. We keep sensitive details out of the notification text and let the app fetch them securely when it opens.
Every endpoint we build is described in OpenAPI and documented for the teams that use it; see our API documentation guide.
Offline, sync and older app versions
Mobile backends have problems web backends do not. Users work on trains and in basements, so the app saves changes locally and the backend receives them later, sometimes after someone else changed the same record. The sync design decides, per kind of data, whether the last change wins, changes are merged or the user is asked. And users update apps on their own schedule, so the API serves several app versions at once: new fields are added without breaking old clients, and an old version that can no longer work safely is asked to update with a clear message rather than failing silently.
Built to be run, not only built
A backend is a service that runs every hour of the year. Ours come with monitoring and alerts, structured logs, error tracking, automated deployment without downtime, database backups that are restored in tests, and documentation of how it all fits together. Runtimes are kept on supported versions: Node.js, for example, states on its releases page (read 11 November 2026) that production applications should only use long-term support releases, which typically get critical fixes for 30 months, and Microsoft's .NET support policy (read 11 November 2026) gives its long-term support releases three years. Upgrades are planned in the maintenance plan, not left until a version runs out of support.
EU hosting and your data
The backend runs in an EU region of a major cloud provider as standard, in your company's own account. The database, backups, logs and uploaded files stay in that region. We document every subprocessor, from the cloud to the email and push services, for your privacy notice and for the questionnaires your business customers will send. A data processing agreement covers our own access, which you can revoke at any time.
How we build it
- Scope. The app's features translated into backend parts, data, integrations and the store rules that apply, with what the first version leaves out.
- Fixed price per phase, in writing. Each phase has a fixed scope and price.
- API first. The API is designed and documented before the screens that use it, so app and backend can be built in parallel.
- Two-week rounds. A working backend on a test environment every round, used by the test version of the app.
- Launch and run. Monitoring live, load checked against expected use, and then development, operation and upgrades on a plan, or handover to your own team.
The backend is usually part of a larger project: see mobile app development, cross-platform app development, API integration for connecting existing systems, outsourcing SaaS development for multi-tenant products and mobile app maintenance for running it afterwards. See prices.
Questions we get
What is backend app development?
Building the server side of an app: the API the app talks to, user accounts and sign-in, the database, file storage, push notifications, payment and subscription checks, background jobs, an admin panel and the integrations with other systems. The app on the device shows things and takes input; the backend stores, checks and connects.
Does every app need a backend?
No. A tool that keeps its data on the device, or syncs through the user's own iCloud or Google account, may need none. As soon as users have accounts, share data with each other, pay for subscriptions you need to verify, receive notifications triggered by events, or work with your company's systems, it needs one.
Should we use Firebase or Supabase, or a custom backend?
A backend-as-a-service such as Firebase or Supabase is quick to start and handles sign-in, data and storage for you. A custom backend gives full control over the data model, business rules, hosting region and costs at scale. Many apps combine them: managed sign-in and storage, with custom services for the business logic. We decide per project and write the reasons into the scope.
What do the app stores require from the backend?
Apple's App Review Guidelines require apps that support account creation to offer account deletion within the app, and Google Play requires an in-app path and a web link where users can request deletion of their account and associated data. The deletion has to happen on the backend, across every system that holds the user's data, so it is designed in from the start.
Where is the backend hosted?
In an EU region of a major cloud provider as standard, in your company's own account. The database, backups, logs and file storage stay in that region, and the list of subprocessors is documented for your privacy notice and your customers' questionnaires.
Get a written quote
Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.