DRAKIX

How we work

From the first study to the system going live

The five stages of a project, what we build with, and what is checked before anything goes live.

Method

From diagnosis to operation

  1. 01

    Diagnosis

    We study the operation, its flows and critical points before any technical decision.

  2. 02

    Architecture

    The entire system is designed and documented: data, integrations, security and scale.

  3. 03

    Design

    Every screen is drawn and approved before implementation. Nothing reaches the code unplanned.

  4. 04

    Engineering

    Built in verifiable cycles, with partial deliveries and clear acceptance criteria.

  5. 05

    Operation

    Testing, publication and full handover: repository, documentation and infrastructure.

Technology

What we build with

Interface

  • React
  • Next.js
  • TypeScript
  • three.js / WebGL
  • GSAP
  • Tailwind

Server and data

  • Node.js
  • PostgreSQL
  • Prisma
  • Redis
  • REST and GraphQL APIs

Infrastructure and security

  • Vercel
  • Docker
  • CI/CD
  • OWASP Top 10
  • Cloudflare
  • Dependency auditing

Before publishing

What is checked before your site goes live

  • It works on your client’s device

    Checked on fourteen devices, from an old phone to a tablet, before every publication.

  • Nothing opens half-loaded

    Content is only released once everything has arrived, so no one meets a missing or frozen screen.

  • It works without a mouse

    Anyone navigating by keyboard alone, or with a screen reader, reaches everything.

  • It is attacked before it goes live

    We try to break into the system ourselves before publishing, to find the flaw before someone outside does.

  • It fits the screen in every language

    The text is checked in all six languages, because the same sentence in German takes almost a third more room. No screen is approved in one language alone.

  • No file is left behind

    The list of what has to load is checked automatically. A forgotten file would make the opening bar promise what has not arrived yet.

  • What changes does not break what already worked

    Before every publication the screens are measured again, so a fix in one place does not overflow the text in another.

Talk to the people who design.