UnlockSFX
Game sound effects from a written description.
- A public developer API
- Credit billing through Stripe
- Unity and Godot editor plugins
Custom software & SaaS development.
We build web applications, customer portals and SaaS products, usually in Next.js, TypeScript and PostgreSQL. That covers the screens people use and everything they depend on: permissions, data, billing and deployment.
What we build
Most of it starts as work done by hand: a spreadsheet nobody trusts, or a request typed in twice.
We turn that into a web application, usually in Next.js, TypeScript and PostgreSQL.
For example: a customer portal
A customer
Signs in to their account.
Your application
Checks permissions on every request.
PostgreSQL
Keeps each customer’s data apart.
From your application: if they pay
Stripe
Payment changes their access.
If your team already runs a stack that works, we use that.
The parts that aren’t on the screen
If an off-the-shelf product already does most of it, we’ll say so.Tell us about the product How a project runs
We run our own products
We built UnlockSFX and UnlockAbode, and we still run both. Larger builds are shared with QC Devworks, and we say who does what.
UnlockAbode
Property software for independent landlords, in public beta.
- A separate workspace per landlord
- Landlord and tenant portals
- A double-entry ledger
Common questions
Can you build a SaaS MVP?
Yes. We define a first release around a complete customer workflow, including the permissions, data model, and operational details it needs. Billing, migration, and ongoing support are included only when they are part of the agreed scope.
Can you improve an application another developer started?
Yes. We first review the repository, deployment, dependencies, and data model. If the foundation is usable, we build on it. If it needs repair, we explain the findings and prioritize changes before adding more features.
Do we own the finished code and accounts?
Ownership, access, and handover are covered in the written project agreement. Our delivery approach puts the repository, deployment accounts, and documentation under an agreed owner so the product can be maintained after launch.