Skip to content
cirlume.
Menu

Back end / 6 technologies

The services, rules and data behind the screens.

A back end decides who can see what, keeps records consistent and talks to the other systems your business runs on. We write it in Node.js, Go or Python depending on the work. When a managed back end gets a product to users sooner, we start on Firebase or Supabase instead.

Start a project

What we use

Back end technologies we know well.

Why us

What we bring to back end work.

  • Go services in production

    Our own products run small Go services on AWS Lambda, so we know how they behave under real use.

  • Managed or custom, chosen openly

    We compare Firebase, Supabase and a custom back end against your data and access rules, and write down why one wins.

  • Built to be handed over

    Readable services, recorded decisions and deployment notes, so your own developers can take the work on.

What you get

What a well-chosen stack gives you.

  • Clear API contracts

    Typed, documented endpoints that front ends and partners can build against.

  • Permissions in one place

    Access rules checked on the server for every request, never left to the app.

  • Slow work off the request

    Queues and background jobs for imports, exports and emails.

  • Integrations that fail safely

    Retries, idempotent requests and logging for calls to payment, CRM and accounting systems.

Where AI fits

AI in back-end work.

  • Model calls from your services

    Node.js, Go and Python all have official SDKs from the major model providers, so AI steps sit inside your existing services.

    AI workflow automation ↗

  • Evaluation pipelines

    Python’s data tooling makes it the usual choice for scoring a model against real examples before and after release.

    AI evaluation & testing ↗

Where it stops: Retries, timeouts and fallbacks matter more for model calls than for most APIs, and every result that changes a record is validated first.

Choosing between them

Which one, and when.

Node.js when the team already writes TypeScript. Go for small, fast services that are easy to deploy. Python where data processing or AI models do the heavy lifting. Firebase or Supabase when sign-in, storage and live data are most of the job. Better Auth when a custom back end needs sign-in that keeps users in your own database.

What’s changing

Shifts to plan for.

Dates that affect back end technologies, checked against the official sources.

  1. July 2026

    Vercel acquires Better Auth

    Vercel announced it is acquiring Better Auth. The library stays free and MIT-licensed, with the same team leading it and a new focus on identity for AI agents.

  2. October 2026

    Python 3.10 reaches end of life

    Security fixes for Python 3.10 end on 31 October 2026, so services and scripts still on it need a newer version.

  3. April 2026

    Node.js 20 reaches end of life

    The Node.js project stopped security fixes for version 20 on 30 April 2026. Services should move to Node.js 22 or 24.

Common questions

Back end questions.

Do we need microservices?

Rarely at the start. One well-structured service is easier to build and run. We split parts out when there is a clear reason, such as very different scaling needs.

Can you connect to our existing systems?

Usually. We review the APIs, exports and sign-in methods those systems offer, then design the integration around their limits.