The thing your business does that no product has a field for
Every company has one. A calibration record, a permit, a sample, a claim, a site survey — the object your process revolves around and that no vendor thought to model. It ends up in a spreadsheet, and the spreadsheet quietly becomes critical infrastructure that nobody owns.
In Capitán you define that object yourself: its name, its fields, which are required, which must be unique, which are indexed, and how it relates to things the platform already knows about. Then the platform builds it.
A real table, not a bag of custom fields
This is the part that matters and the part most no-code tools skip. Capitán generates an actual database table in its own schema, with a primary key, real unique constraints and real indexes, audit columns recording who created and changed each row, and a foreign key to the company that owns it — so tenant isolation is enforced by the database rather than remembered by the application.
Your object can point at built-in platform records as well as at other objects you have defined. A custom inspection can belong to a real work order; a custom permit can reference a real employee. It is a first-class part of the data model, not an attachment bolted onto the side of one.
Everything else follows automatically
Because the rest of the platform is metadata-driven, defining the object is the whole job. It gets its own screens and menu entries, and can opt into file attachments, media, tags and an activity feed with a checkbox each. Your automations and validation rules target it like any other record, it appears in reports and dashboards, it works on mobile, and it is reachable through the same API — including by an AI agent through our MCP server.
The spreadsheet became critical infrastructure because modelling it properly needed a development project. It does not any more.
Custom objects are configuration, not code. They survive upgrades, they are visible and changeable by the people who own the process, and there is no bespoke module to maintain when its original author moves on.
