Internal tools and workflows
Case, document, research and operations tools designed around real roles, approvals, audit needs and export paths.
Custom software engineering
Purpose-built software, delivered with a proof trail.
ANULUM designs, builds and improves software for confidential, scientific and operational work where a generic product does not fit. The engagement begins with the decision and acceptance boundary—not a fashionable stack.
01Scope frozen02Risks mapped03Tests recorded04Handover accepted
What we can deliver
One bounded system, a difficult component or a measured improvement to an existing product.
AI and retrieval integration
Local or policy-gated model workflows, source-grounded retrieval, evaluation, human gates and observable failure behaviour.
Scientific computing
Reproducible data pipelines, numerical services, experiment tooling and interfaces that keep assumptions and provenance visible.
APIs and system integration
Versioned interfaces, identity boundaries, data validation, event flows and migration paths between legacy and modern systems.
Performance engineering
Profiling before optimisation, recorded baselines, bounded changes and measured latency, throughput or resource improvements.
Maintenance and recovery
Dependency stewardship, controlled releases, backup and restore, incident records and support terms agreed for the actual system.
The engineering contract
| Decision | Evidence at acceptance |
|---|---|
| Problem and scope | Named users, workflows, exclusions, dependencies and acceptance scenarios |
| Architecture | System and data boundaries, threat assumptions, important trade-offs and recovery path |
| Implementation | Versioned source, review record, automated checks and reproducible build instructions where applicable |
| Quality | Agreed functional, security, performance and failure tests with recorded results—not a universal coverage slogan |
| Handover | Runbooks, ownership, licences, credentials boundary, known limitations and accepted backlog |
| Change and exit | Release, rollback, export and transition path that does not depend on silent vendor custody |
How an engagement moves
- Confidential discovery Identify the costly decision, users, data, constraints and what must not happen.
- Architecture and written scope Fix the deliverables, interfaces, evidence gates, responsibilities, commercial basis and stop conditions.
- Incremental build Demonstrate working slices against agreed scenarios; record changes and unresolved risks.
- Acceptance and handover Run the agreed tests, transfer the operating record and decide whether to stop, extend or support.
Rates and package boundaries remain in the dated pricing registry; the written scope controls every engagement.
Where private AI meets software
A model is one component, not the product.
Useful systems also need identity, ingestion, retrieval, workflow, audit, evaluation, recovery and a human decision boundary. ANULUM can integrate those layers into the software people actually use.
Inspect the engineering practice → Review the security service →