// Forja · Pillar 03
The platform
we already use.
Forja is our service engineers' daily tool. It was born to organize what happened in the field and is now ready for teams facing the same mess.
// Status
Daily use
We use it every day. Not a demo, not a roadmap.
// Stack
Next.js · tRPC · Prisma
Deployed on Vercel, managed database, authentication with Clerk.
// Origin
Built in the field
Every feature answers a real case documented by our technicians.
// What it does
Four functional blocks.
Structured diagnostics
Forms per product line that guide the technician step by step, with attachments and a log.
RMA and spare parts
Traceability of units sent to warranty. Status visible to the customer and the warehouse.
Procedures and notebooks
Runbooks versioned per model, with real photos and videos captured in the field.
Operational data
What happens in service feeds the next commercial and catalog decision.
// Where it fits
Use cases.
In-house service teams
For companies with internal technicians who track everything in spreadsheets today.
Brand operators
When a manufacturer wants to see what happens to their equipment after the sale.
Wearable integration
Forja runs on the hands-free headset: the technician dictates, the log fills itself in.
For now we open Forja to a small group of teams. The conversation starts with a concrete case and a clear metric of what you expect to solve.
// Get started
Tell us what mess you want to organize.
If you rely on spreadsheets, WhatsApp, and the technician's memory today, let's talk.