Skip to main content
Allways

Web platforms, process automation and AI systems. A private repository in your name from the first commit. Documentation and handover on delivery. Without being tied to whoever built it.

See how we work
WHAT YOU CAN OPEN

Take none of it on trust.

What we built for ourselves is right here, and you can open it today without talking to anyone.

THIS PAGE

This site

It is built to the same standard we build to for you. Do not take our word for it: measure it.

Measure this site on PageSpeed Insights, mobile view
OUR OWN ENGINE

A graphics engine of our own, with no third-party libraries

We wrote our own graphics engine, with no Three.js and no 3D library at all. Its simulation is deterministic: the same input produces the same result byte for byte, on any machine. With the repository in hand it takes one command to check: `npm run repro` has to print the same seal every time.

TOOLING

Our own tools

We build the internal tools we work with. Whatever we use on your project, we used on ours first.

DELIVERY

How we hand over

Repository in your name, technical documentation, a test report and a recorded handover.

See all case studies
WHAT WE BUILD

From the server to the screen.
One owner.

6 disciplines wired to each other. When something breaks, nobody has to work out whose fault it is: there is one repository, one named technical lead and one direct channel.

Every project ships with the repository in your name, the technical documentation and a recorded handover session.

Technologies we work with

Next.js
React
TypeScript
Python
Tailwind CSS
Vercel
Supabase
PostgreSQL
Docker
Node.js
Framer
Kubernetes
Figma
GitHub
AWS
HOW WE WORK

5 stages.
You know what happens in each one.

A typical project: 1 to 3 weeks depending on scope. The date of each stage is fixed in writing before we start.

Discovery

Scoping workshopsCompetitive analysisUser interviews

We work out the business, who is going to use it and what has to happen for it to be worth having. You leave with the scope closed and the architecture decided, before the first line of code.

You get

  • Scope and priorities in writing
  • Validated user stories
  • Architecture diagram

Design

FigmaFigJamProtopie

We define every screen and every state, including what you see when something fails or there is no data yet. You approve it before anything gets programmed.

You get

  • Clickable prototype
  • Component system
  • Acceptance criteria per screen

Development

Next.jsTypeScriptCI/CD

We build in increments. Every week there is something working that you can open and try, not a screenshot in a meeting.

You get

  • Your own test environment
  • Reviewable progress every week
  • Repository in your name from the first commit

Testing

PlaywrightLighthouseWCAG

We test against the cases that break things: empty data, dropped connections, two people doing the same thing at once, heavy load. And we write down what was tested.

You get

  • Test report
  • Automated tests in the repository
  • Accessibility and performance review

Launch

VercelDatadogAnalytics

It goes to production with monitoring, backups and a recorded handover session. The credentials and the repository stay in your name.

You get

  • System in production
  • Operations manual
  • Recorded handover session
WHAT WE SIGN

Three commitments that go into the contract.

We sign them in writing before we start, with their definitions and their limits. They do not stay on this page.

COMMITMENT 01 / DELIVERY DATE

The delivery date is fixed in writing

Before we start we agree the date of each stage and what compensation applies if we are late for a reason of ours. It goes in the contract, not in a promise on a web page.

Where you can check it

COMMITMENT 02 / OWNERSHIP

Repository, documentation and handover, in your name

A private repository in your name from the first commit, technical documentation and a recorded handover session. The exact scope of the transfer is fixed in writing in the contract, before we start.

Where you can check it

COMMITMENT 03 / ATTENTION

You talk to whoever builds it

Your project has a technical lead with a first and last name, a direct channel and a reply within 24 business hours for the whole project. No account managers translating in between.

MEASURED, NOT PROMISED

Four numbers from this very page,
each one with the file that measured it.

We do not publish our provider uptime or the speed of your connection: we do not measure those. These four we do, and we measure them again on every delivery.

LAYOUT SHIFT
0.000
Nothing moves while the page loads. No button sliding out from under your thumb.
probe-cls.mjs · 12 s · 1440 px · /es
CONTRAST FAILURES
0
Across 5,284 text nodes on the thirty routes. All of them above the AA minimum.
recon-a11y.mjs · 30 routes
THIRD PARTIES BEFORE CONSENT
0
Not one outside domain, not one cookie, until you accept. Fifteen seconds at rest, measured.
probe-terceros.mjs · /es/contacto
ACCESSIBILITY ERRORS
0
Automated axe violations on the thirty routes. The manual review is separate.
recon-a11y.mjs · axe-core

Measured against the production build. Every number is checked against the file that measured it, and that check runs with the test suite: if a number stops being true, the check fails.

First reply within 24 business hours

Tell us what you need
to build.

30 minutes with the person who will design the solution. If it is not a fit, we tell you on that same call. First reply within 24 business hours.