About
We build and run software for institutions where a failure is a reportable event. No account managers, no delivery layer, no bench.
Why we exist
[Founder] spent [N] years building [specific system] at [institution]. The recurring problem was not technology — it was that the firms capable of the engineering did not understand the regulation, and the firms that understood the regulation subcontracted the engineering. ScaleJade exists to be one team that does both.
How we work
Engagement models
We offer [two/three] engagement models: [fixed-scope delivery for well-defined projects, embedded team for ongoing product work, and managed operations for systems that need to run]. Each starts with the same question: what cannot fail, and what happens when it does.
Team composition
A typical engagement is [N] engineers, one of whom is a principal, for [N] months. You get the people you met in the scoping call — not a different team on day one. No juniors billed at senior rates, no offshore handoff.
What the client owns
You own the code, the documentation, the infrastructure configuration, and the IP. Every engagement includes a handover package written during the build — not assembled at the end — so your team can operate and extend the system without us.
How we start
We begin with a [two-week] paid discovery. We study your architecture, your constraints, and your existing team. At the end you receive a scoping document with a fixed timeline, a fixed team, and a fixed price. If we are not the right fit, we tell you and you owe nothing further.
What we're built on
Standard SLA: [response time / uptime commitment]. On-call model: [description]. Incident review policy: [description]. Measured uptime across engagements: [metric].
ISO 27001 status: [certified / in progress, targeting QX 20XX]. Penetration-test cadence: [frequency], performed by [firm]. Client data hosted in [jurisdiction]. Production access: [who holds it, under what controls].
Frameworks we have built against: [POJK / MAS TRM Guidelines / UU PDP No. 27/2022 / PDPA / ISO 20022 / others]. We design and document to the named regulation, not to a generic 'compliance-ready' claim.
Source-code escrow: [provider, terms]. IP ownership: the client owns it, stated in contract. Documented handover policy: included in every engagement. If the firm ceases trading: [your code, your infrastructure, your migration path].
The facts
Research
Our research preprints are authored by the people on this page. We publish in the open because the institutions we serve need to see the work before they trust the implementation.
Read our researchJoin us
We hire occasionally and deliberately. If you build production systems in regulated environments and you want to work on problems where correctness is non-negotiable, introduce yourself.
Talk to us