backends

The part underneath

APIs, databases, logins and hosting. Usually bought alongside a site or an app, sometimes on its own when what you have already works but cannot take the load.

what it is built with

  • Kotlin and Ktor

    Typed end to end, with coroutines instead of a thread per request.

  • PostgreSQL

    The boring choice, on purpose. Constraints in the database, not in hope.

  • Redis

    Caching, queues and pub/sub for anything that has to be instant.

  • Entra ID and Discord SSO

    People sign in with an account they already have.

what you get

  • 01

    Events that fan out

    Redis pub/sub, so a new ticket, an invoice or a status change reaches every service that has to act on it the moment it lands. The portal you would log into runs on this.

  • 02

    Who can see what

    Roles and permissions checked on the server, on signed tokens that can be revoked. Not a hidden button on the client.

  • 03

    Deploys that do not take the site down

    Containers, rolling updates and a health check that has to pass before traffic moves. Failed deploys roll back on their own.

Backend work is scoped per project rather than sold in bands. Describe what it has to handle and you get one number back.