Structured data model
Tables, relations, constraints and indexes generated from your process description, so the data stays clean instead of degrading into free text.
Describe the process you run today — the tracking sheet, the shared inbox, the folder of PDFs. Cadrant turns it into a real internal tool with a Postgres database, roles, permissions and dashboards, hosted on your own Supabase project.
Your database · Roles and permissions · Code exportable
An internal tool builder is a platform for the software a company runs on but never sells: back-offices, admin panels, client portals, operations dashboards, approval workflows. These tools rarely justify a full development project, so they usually end up as a spreadsheet, a shared inbox and a lot of manual copying.
Cadrant builds them from a description of the process. You explain who does what, what gets recorded and who is allowed to see it; Cadrant generates the data model, the screens and the permission rules, and connects them to a Postgres database in your own Supabase project.
The difference from a no-code table tool is where the tool ends. A generated Cadrant project is a conventional React + Supabase application: it can be reviewed by your IT team, extended by a developer, and deployed on your own infrastructure the day the tool becomes critical.
Not just forms and tables: the access rules, the exports and the integrations that decide whether a tool gets adopted.
Tables, relations, constraints and indexes generated from your process description, so the data stays clean instead of degrading into free text.
Admin, manager, agent, read-only — enforced by Supabase Row Level Security at the database level, not hidden in the interface.
Lists with filters and search, detail pages, status pipelines and the aggregate figures your weekly meeting actually asks for.
Give external users their own authenticated space, scoped to their records only, without exposing the rest of your back-office.
Upload contracts, photos and PDFs into Supabase Storage, attached to the right record with public or private access policies.
Edge Functions for scheduled jobs, notification emails, Slack messages, webhooks and calls to the APIs your company already uses.
Start with the workflow you already run — the tool is a formalisation of it, not a reinvention.
Who does what, in what order, and what has to be recorded. Paste the columns of your current spreadsheet if that is faster.
Link your Supabase project. Cadrant creates the schema, the roles and the Row Level Security policies inside your own database.
Invite colleagues, check each role sees only what it should, then adjust the screens in conversation as real usage exposes the gaps.
Deploy behind your domain over HTTPS, and sync the repository to GitHub so your IT team can review, extend or take over the code.
If it currently lives in a spreadsheet and three email threads, it belongs here.
The point of an internal tool is that it can be audited, reviewed and kept. That requires a stack, not a black box.
Your operational data in a standard Postgres database on your own account, queryable with SQL and backed up on your terms.
Access rules live in the database, so a misconfigured screen cannot leak rows a user was never meant to read.
Server-side logic for integrations and scheduled jobs, with API keys and credentials kept out of the browser.
A React + Supabase repository your developers can review, extend and deploy on your own infrastructure.
An internal tool ends up holding the records the company runs on, and that is exactly the data you cannot afford to rent. You connect your own Supabase account, so the database, the backups and the access rules are governed by you rather than by us.
It is a platform for building the software a company uses internally rather than sells: back-offices, admin panels, dashboards, client portals and approval workflows. Cadrant generates them from a description of your process, with a real database and permission rules rather than a shared file.
In your own Supabase project, in the region you choose, on your own account. Cadrant reads and writes through your project credentials; your records are never mixed into a vendor-owned multi-tenant table.
Yes, and it is enforced where it matters. Cadrant generates Supabase Row Level Security policies, so the filtering happens in the database rather than in the interface. A user cannot reach rows outside their scope even if a screen is misconfigured.
No. Cadrant is billed as a flat monthly plan for the person building the tool, not per editor or per colleague using it. That is usually the difference between a tool one team uses and a tool the whole company uses.
Yes, through Edge Functions: any HTTP API, webhook, notification email or scheduled job can be triggered server-side, with credentials stored as environment variables rather than in the front end.
From the Pro plan the project syncs to GitHub as a standard React + Supabase repository. Your developers can read it, run it locally, open pull requests and redeploy it on your own infrastructure.
The Starter plan is $20 a month and covers up to 5 projects, hosting and a custom domain. The Supabase integration is available on every plan, including the free one. Building and testing is free with the 10 free credits you get at signup, so you can validate the tool with your team before paying.
Describe the process once, watch the tool appear, then adjust it with the people who use it every day.