Forja: the workshop where we build everything else

Forja is our engineering platform: the board where every piece of work is a task with an owner, the team of AI assistants working under human supervision, the quality gate that stops what isn’t ready, and the memory of what we learn. Every system we deliver goes through it.

2,073
commits since 09/16/2026
8,165
automated tests
587
API routes

Measured on October 21, 2026 on Forja’s codebase and its board.

Demo · the journey of a request

One request, from idea to production

This is how a piece of work travels through Forja, step by step. The request is a sample; the steps are the ones we follow on every project.

Forja was born from a concrete need: working with several people, several machines and AI assistants at the same time without anyone stepping on someone else’s work, and without losing track of who did what.

Today it’s where everything lives: the task and sprint board, the lanes that say who is touching which file, the questions the AI can’t decide on its own, and the quality gate that runs before every push. We use it every day to build our clients’ systems, and to build Forja itself.

It isn’t a product we sell today: it’s the reason we can promise quality. The same discipline you see here goes into every project we deliver.

Every piece of work is a task with an owner and a closing note
AI works in lanes and a person decides
No change ships without passing the quality gate
What we learn gets written down and reused

Capabilities

Board, sprints and lanes

Every piece of work is a task with an owner, priority, due date and closing note. Before touching code, the lane is declared: who touches which files, so two people don’t collide.

Supervised AI assistants

Assistants work on their own copy of the code and claim their task. Whatever needs a person goes to “To decide”: a permission, a question, a delicate change.

Forja Sync

The connector installed on every team machine: it sets the machine up, brings in everyone else’s work and tells Forja what is being done.

Vault and REUSE catalog

Notes on what we’ve learned and a catalog of already-tested code pieces: before writing something new, we check whether it already exists.

Code graphs

Every repository indexed as a graph of functions and calls: you can understand a system without reading all of it.

Quality gate and lock

Lint, types, tests and build in Docker before every push. The lock spreads heavy test runs so machines don’t choke.

Pages and site builder

A page space for documents, reports and number sheets, and a site builder with versions.

Forja Marketing

A separate area for the marketing team, with its own board and no access to the code.

Calls and meetings

Calls and meetings inside Forja, with team chat and updates that reach every machine.

Multi-organization

Each organization with its members, its permissions and its own database: one can’t see into another.

Forja from the inside, in numbers

Counted on Forja’s codebase, the same one running in production. It includes the work of our two organizations.

2,073
commits in its history, since the first one on September 16, 2026
git, main branch · 10/21/2026
85%
of those commits declare AI assistance; a person reviews and signs each one
1,768 co-signed · 10/21/2026
587
API routes, each with its organization check
Backend code · 10/21/2026
126
data collections, each with its validated schema
Data model registry · 10/21/2026
92
tools that let AI assistants work with the board
Forja MCP server · 10/21/2026
353
board tasks cited in those commits: every change says which piece of work it answers to
git, main branch · 10/21/2026

Automated tests

Test functions in every part of Forja. They run in Docker before every push; if one fails, the change doesn’t ship.

8,165

tests in total, plus 83 quality gate probes

Forja codebase · 10/21/2026

Server (API and data)3,288
Web interface2,845
Forja Sync connector and MCP2,032

The board, today

A snapshot of the Forja project on its own board, taken while measuring.

27
tasks closed in the master plan sprint
Forja · 10/21/2026
5
assistants working at once, each in its own lane and task
Forja · 10/21/2026, 00:45
5
tasks in review: none becomes “done” without its closing note
Forja · 10/21/2026
28
days with commits since it started
git · 09/16 to 10/21/2026

What we don’t measure yet

How many hours Forja saves us and how many deployments it has gone through don’t come out of a command we can show yet. Once we measure them with the same care, we’ll publish them here with their date.

Numbers

Want to work with a team that measures itself like this?

Forja is internal, but its discipline goes into every project: tasks with an owner, tests on every change and people who answer for it.

Let’s talk about your project