Lumium for banks
Agent work that never leaves the perimeter.
Regulated finance already has the deployment shape: everything inside the network, everything on the record. Lumium adds an agent workspace to that shape instead of asking you to change it.
The same conversation, every quarter
A team tries a hosted coding agent, likes it, and then the data-processing review stops it. The next attempt is a local model wrapper that one engineer maintains and nobody else wants to operate.
Neither outcome is an agent platform. One puts your source in someone else's tenancy; the other puts an unowned script in your critical path.
Lumium keeps the parts that made the hosted tool useful, a console where people and agents work in the same place, and removes the part that fails the review: the tenancy. You run it, you hold the keys, and the ledger is a table in your database.
What your reviewers will ask
Data residency
Every conversation, artifact, work item, and file record lives in the database you operate. The only outbound traffic is a model call you configured yourself.
Evidence for audit
Run outcomes, authority operations, and ledger entries are durable rows with an organization-wide sequence, queryable with plain SQL.
Model approval
Register only the models your review board approved. A project gets an allowlist, not the whole catalog.
Access control
Project membership decides who reads and writes. An agent works with the permissions of its project assignment, never its owner's.
What you actually deploy
- One Node process inside your network
- SQLite or libSQL database you already back up
- Local object storage, or S3-compatible when you need it
- Model registry with a per-project allowlist and your own keys
- Project membership as the authorization boundary
- Encrypted secrets that never enter prompts or logs
- Ledger records with an organization-wide sequence
- Approval-gated, audited tool calls
- No telemetry of its own
Lumium is in early access. There is no certification to point at yet, and nothing on this page should be read as one.
Who this is for
CISO
A runtime whose boundary is a network diagram they already approved.
Head of platform
One deployable artefact instead of a bespoke agent wrapper.
Engineering manager
A workspace the team uses daily, inside the existing change process.
Internal audit
Records they can query themselves, without a support ticket.
Start with one team, not one transformation.
Pick a project, deploy it inside your network, and run a first conversation against an approved model. Talk to us if you want a deployment review before that.
Talk to us