Custom business software / Private systems and applied cryptography
Keep private things private. Keep the keys deliberate.
Private communication and protected business records, scoped around established cryptographic primitives, explicit access, key handling, retention, and recovery.
Start with the way the work happens.
Privacy is an engineering boundary. Decide what a system needs to know, who can see it, where plaintext is permitted, and who holds the keys. The right design depends on the actual threat model and the practical needs of the people using it.
- Private communication and protected records
- Established cryptographic primitives
- Explicit data and access boundaries
- Key lifecycle, recovery, and retention requirements
Define the uncomfortable parts first.
Encryption does not answer every security question. The scope must address authentication, endpoint access, key storage, recovery, and the system around the cryptographic primitive. Independent review or audit requirements should be agreed explicitly; we do not imply a certification or completed audit.
- A written threat and data-boundary discussion
- Named key holders and recovery responsibilities
- Deliberate third-party and retention decisions
- Source, documentation, and a handoff you can inspect
A workflow you can try
The product lab uses clearly labelled sample records to show a workflow from the perspective of an owner, operator, engineer, finance team, or support team. Run a normal path, inspect the record behind it, and turn the result into an editable starting brief. The lab is a guided demonstration; it is not a connected customer system.
The first useful scope is specific to your operation. Hosting, third-party services, and any optional ongoing support are discussed separately from the fixed build price.
A better way to work starts here
Let’s make it
work for you.
Bring the spreadsheet, the workaround, or the platform you’ve outgrown. We’ll start with what your business actually needs.
Discuss your build