Skip to content
BACKEND & APIS

The systems underneath your product.

APIs, data pipelines and services that stay fast and predictable under real load. Python where the logic lives, Rust and Go where speed matters.

01 PROBLEMS

Problems we solve

Where most of these projects start.

  1. 01

    Systems that don't talk

    Your team re-keys orders between the shop, the CRM and the accounts system.

  2. 02

    A backend holding the product back

    New features wait on a backend that is slow to change and hard to test.

  3. 03

    Slow when it matters

    Requests slow down or time out when traffic picks up, and nobody can see why.

  4. 04

    Costs that keep climbing

    Your cloud bill grows faster than your usage, and it's unclear which service is the cause.

02 BUILD

What we build

APIs

REST and event-driven APIs with documentation and auth.

Integrations

connect payment, CRM, ERP and messaging systems.

Data pipelines

move, clean and store data on a schedule or in real time.

High-performance services

Rust or Go where latency and memory matter.

Background jobs

queues and workers for the slow tasks your users shouldn't wait on.

03 DELIVERABLES

What you get

Everything lands in your accounts. Nothing stays locked with us.

  • Source code in a repository in your account
  • Versioned API schemas and reference docs
  • Automated tests, including tests against each API contract
  • A CI pipeline that builds, tests and packages each change
  • Docker images and deployment scripts
  • Logs, metrics and error tracking, set up and working
  • Database migrations and seed data
  • A runbook for deploys, rollbacks and common failures
04 EXAMPLE

A typical project

An example scope, not a client project.

The brief

An integration service that syncs orders from your online shop into your CRM and accounting system.

In scope

  • Order sync from the shop to the CRM
  • Invoices created in the accounting system
  • Retries and alerts when a sync fails
  • A small API for your team to check sync status
  • Deployment with logs and metrics

Milestones

  1. Contract

    The API schema and data mapping are agreed, with a mock API you can call.

  2. First sync

    New orders from a test shop appear in the CRM.

  3. Full flow

    Invoices post to accounts, failed syncs retry and alerts reach your team.

  4. Handover

    Runbook, dashboards and deployment scripts are in your accounts.

05 STACK

Tools we work with

The tools we know well for this work. The spec names the ones your project uses, and why.

Our default picks 45 tools · chosen per project in the spec
  • Languages

    • Python (default pick)
    • TypeScript
    • Go (default pick)
    • Rust (default pick)
  • Frameworks

    • FastAPI (default pick)
    • Django
    • Node.js
    • NestJS
    • Hono
    • Axum
    • Gin
  • Interfaces

    • REST
    • GraphQL
    • gRPC
    • WebSockets
    • OpenAPI
    • Webhooks
  • Databases

    • PostgreSQL (default pick)
    • MySQL
    • MongoDB
    • Redis (default pick)
    • ClickHouse
    • DynamoDB
  • Queues and workflows

    • Celery
    • BullMQ
    • RabbitMQ
    • Kafka
    • Amazon SQS
    • Temporal
  • Infrastructure

    • Docker (default pick)
    • Kubernetes
    • Terraform
    • GitHub Actions
  • Cloud

    • AWS
    • Google Cloud
    • Azure
    • Cloudflare
  • Observability

    • OpenTelemetry
    • Grafana
    • Prometheus
    • Sentry
  • Security

    • OAuth
    • JWT
    • Keycloak
    • HashiCorp Vault
FAQ

Common questions

How do you choose between Python, Rust and Go?

Python by default for business logic. Rust or Go where speed or memory matters. The spec explains the choice for each service.

Can you work with our existing backend?

Yes. We can extend it, add services beside it, or replace parts of it step by step. Discovery decides which.

Which systems can you integrate with?

Anything with an API, a database or a file export: payments, CRM, ERP and messaging. If a system has no API, we set out the options in Discovery.

Do you document the API?

Yes. Reference docs are generated from the schema, so they stay in step with the code.

Have something to build?

Tell us what you're working on. We reply within one business day.