Custom software
The proof is what we run
This site, the console behind it and the CAD suite our engineers model in are all ours. You can read the same argument for our work by using them.
What we take on
Applications with a database under them
Web applications
Customer-facing products where the hard part is usually not the page. Accounts, permissions, payments, and everything that has to keep being true after the launch.
Internal consoles
The screens a business actually runs on: queues somebody works every morning, approvals with a record of who decided what, dashboards built from your own numbers rather than an export.
Data and integrations
Schema design, migrations against a database already carrying live data, and the connections between systems that were never meant to talk.
Taking over something already built
Reading an unfamiliar codebase and making it safe to change is its own skill. We do this, and we will tell you honestly when a rewrite is cheaper than a rescue.
Built here
Two things you can go and look at
This platform
TypeScript on Next.js, Postgres with row-level security so a customer's data is fenced off by the database rather than by a query somebody remembered to write. Stripe billing, a support desk with internal notes, transactional mail with delivery tracking, and a staff console with per-permission roles behind it.
Forge
A parametric CAD suite we wrote: a sketch solver, solid modeling, assemblies, 2D drawings with GD&T, and STEP, DXF and STL export. It is not a product you can buy. It is what our engineers design in, and it is the largest single answer to what this team can build.
Tell us what it has to do
You do not need a specification. What exists today and what you want instead is enough to start the conversation.