ServicesWorkReviewsAboutGet in touch

Backend, API and cloud development

The APIs, databases and infrastructure that everything else stands on.

What we build

Users never see the backend, but they feel it: in how fast the app answers, whether a payment goes through and whether their data is still there tomorrow. We design it first and build it to be changed.

The iMed backend runs orders, staff, availability and notifications on Node.js and PostgreSQL. Safe Appetite runs on Node.js and MongoDB with file storage on AWS.

APIs

REST and GraphQL APIs with clear contracts, built for the apps and partners that call them.

Databases

PostgreSQL and MongoDB, with the data model, migrations and backups thought through from the start.

Accounts and payments

Sign-in, roles and permissions, subscriptions and one-off payments.

Notifications and background work

Push notifications, email and the scheduled jobs that keep a product moving.

Cloud infrastructure

AWS, Firebase and Supabase, set up so it is observable, secure and affordable to run.

Integrations

Third-party APIs connected properly: maps, payments, AI models and the services your business already uses.

How we work

The same four steps on every project, whatever its size.

01

Understand

You tell us what you are building and who it is for. We ask the questions that decide the design before any code is written.

02

Plan

We reply with how we would build it: the parts, the order, the risks we already see and what it would take.

03

Build

One senior team designs, writes and reviews the work in house. You see it running as it grows, not at the end.

04

Care

After launch we keep it healthy with upgrades, monitoring and security reviews, for as long as you need us.

Built with

  • Node.js
  • Express
  • PostgreSQL
  • Prisma
  • MongoDB
  • GraphQL
  • Supabase
  • Firebase
  • AWS

Related work

Projects where this is the work we did.

What clients say

Written by clients, in their own words.

Read all 94 reviews
caregroup_tech
United Kingdom
Fiverr
5.0
I had a great experience on this project! His code quality was clean, efficient, and well-structured. He demonstrated strong expertise across both front-end and back-end, and were able to quickly understand the requirements and translate him into working solutions. The communication was fast and clear, and any revisions or requests were handled with great responsiveness and professionalism. Overall, a very smooth and productive collaboration. I highly recommend this freelancer to anyone looking for a skilled and reliable full-stack developer.
Front-end fixing bugs for web panel
Verified Upwork client
Upwork
5.0
I've had the pleasure of working with Muhammad on several projects, and their backend development skills are truly impressive. They consistently deliver clean, efficient, and well-documented code, and they have a strong understanding of system architecture and API design. Muhammad is also great at troubleshooting and optimizing performance, often identifying and fixing issues before they escalate.
Backend and front end development for Medical App
Verified Upwork client
Upwork
5.0
This was a challenging stage, but Muhammad handled it successfully. The requirements changed during the process, yet the work completed was accurate and well-executed. Ahead lies even more demanding tasks, and I am confident that if Muhammad joins our team, they will be completed flawlessly. He has proven himself not only as a professional but also as someone who suggests optimal solutions for implementation.

Questions

Which backend technologies do you use?

Node.js with PostgreSQL or MongoDB for custom backends, and Supabase, Firebase and AWS for managed services.

Supabase and Firebase, or a custom backend?

Both have their place. Supabase and Firebase get a product live quickly. A custom Node.js backend is the better choice when the rules are complex or the system has to grow in its own direction. We tell you which one we would choose and why.

Can you work on a backend someone else built?

Yes. We start by reading the code and telling you what we found, then fix and extend it.

How do we start?

Send us a few lines about what you are building. We reply with how we would build it and what it would take.

Tell us what you are building.

A few lines are enough. We reply with how we would build it and what it would take.

Start a project