Rakkay Technologies

Service

Backend and API development

The APIs, authentication and data models behind the product. Node and Express where the stack is JavaScript end to end, Laravel where it is not.

Built in
Node.js · Express · PHP · Laravel · PostgreSQL · MySQL

Our approach

How we build them.

  1. The backend decides what the product can do later. We spend the early time on the data model and the API contract, because those are the two things that are expensive to change once clients depend on them.

  2. We work in Node with Express and in PHP with Laravel. Which one a project gets is set out below, criterion by criterion, rather than left to whichever we would rather write.

  3. Either way you get migrations under version control, structured logging, and an API you can read the definition of.

Choosing the stack

Two good answers, one right one.

We work in both, and the choice is made on your project rather than on our preference. This is how we decide.

  • Node and Express

    We reach for it when

    • The front end is already React or React Native
    • You want one language across the whole stack
    • Types can be shared between client and server
    • The team you will hire next writes TypeScript

  • PHP and Laravel

    We reach for it when

    • You already run PHP infrastructure
    • Your existing team knows it
    • A mature, batteries-included framework shortens the build
    • The product is closer to conventional CRUD than to real-time

What you get

Every engagement delivers this.

Written as things rather than intentions, so you can hold the list up against what arrives at the end.
  • REST API design and implementation
  • Authentication, authorisation and role-based access
  • Relational data modelling and migrations
  • Third-party and payment gateway integration
  • Background jobs, queues and scheduled work
  • Structured logging and error reporting

Included

The engineering underneath.

Not add-ons, and not quoted separately. These come with the service because a project that needs them and does not get them is a project that stalls.

  • Performance and scaling

    Profiling and fixing applications that have outgrown their original design, wherever the bottleneck sits — client, server or database.

    • React render profiling and re-render elimination
    • Bundle analysis, code splitting and lazy loading
    • Slow query and N+1 diagnosis
    • Caching strategy and read-path optimisation
    • Core Web Vitals and mobile startup time

  • CI/CD and release engineering

    Automated pipelines so shipping is routine rather than an event, including signed builds for both app stores and staged rollout.

    • GitHub Actions pipelines for build, test and deploy
    • Automated iOS and Android builds with signing
    • Preview environments for every pull request
    • Staged rollout and rollback procedure

Also from us

Not what you need?

The other two, in case this is not the one. Most products end up needing more than one — tell us the whole problem and we will say which you actually need first.

Start with a conversation.

Send us the problem, not a specification. We read every message ourselves and reply personally — and if we are not the right team for it, we will say so and usually point you to someone who is.

  • Read by an engineer
  • Answered personally
  • No sales sequence
Send a message