Web systems & dashboards
Internal platforms, admin areas and dashboards that stay fast as the data grows. Built for the people who use them all day, not for the demo.
What the work covers
The systems nobody markets and everybody depends on: the back office, the operations screen, the report that decides the month.
Admin and back office
The screens your team lives in. Search that finds things, tables that paginate properly, forms that say what is wrong before you submit them.
Dashboards that stay honest
Numbers traced back to a query you can read. Charts that state their period and their filter, so two people looking at the same screen see the same thing.
Roles and permissions
Access by profile, enforced on the server rather than hidden in the interface. What a user cannot see, a user cannot request.
Fast with real volume
Indexes, pagination and query plans checked against production-sized data — not against the twenty rows that exist on the first day.
Login and sessions
Authentication, password recovery, session expiry and audit trails, wired to your existing identity provider when you have one.
Exports and reports
CSV and PDF that match what is on screen, generated without freezing the browser for the person who asked.
What you end up with
- A deployed system with preview environments for every change before it reaches production.
- A documented data model and migrations, so the next developer is not reverse-engineering the database.
- Role definitions written down, with a matrix of who can do what.
- Access to logs and metrics, plus a short guide on reading them when something looks wrong.
The stack we reach for
- React
- TypeScript
- Node.js
- PostgreSQL
- Supabase
- Vercel
- REST
- Playwright
How it runs
Mapping the work
We sit with the people who will use it and follow what they do today, including the spreadsheet everyone pretends is temporary.
Screens before code
Flows and layouts agreed while they are still cheap to change.
Ship in slices
One working area at a time, in production and in use, rather than a big reveal at the end.
Tune and hand over
Performance checked against real volume, then the walkthrough and the documentation.
Questions we get asked
Can it talk to the systems we already run?
Usually yes. If it has an API, a database we can reach or even a scheduled file drop, we can integrate it. We check feasibility before quoting, not after.
Who hosts it?
Your accounts, by default — Vercel, a cloud provider of your choice, or your own servers. We set it up and the keys stay with you.
How many users does it hold?
That depends on what they do, not just how many they are. We size it against your real numbers during scoping and tell you where the first ceiling will be.