Velenza BOC
Secure by construction.
Built by a security architect, from the foundation up, for a system that would hold a company’s most sensitive operational data.
The controls below are not features on a roadmap. They are how the platform works. We are pursuing SOC 2 deliberately rather than scrambling for it; the control map an auditor works through is largely a description of choices already made in the architecture.
Every actionchecked against policy before it runs. Every customerisolated by design.
Every transactiona way to undo it, confirmed before it starts. Every claimgraded against what happened.
Every keypost-quantum wherever Google Cloud offers it in general availability.
Nothing runs without a decision
A decision on every effect, without exceptionEvery action that can cause an effect is checked against the gate, automatically. There is no way for an action to skip it.
You are always the backstopWhat policy clearly allows proceeds on its own. Anything else waits for a person, through the same gate, never a side door.
Always currentA permission you changed five minutes ago is the permission that applies.
Computed, not declared
Derived from the factsThe decision comes from the facts of the action, the policy and the identity asking. There is no priority field for an integration to set wrongly.
Cognition never touches stateThe reasoning half proposes. A separate deterministic layer owns every effect and every byte of stored state.
Nothing starts with write accessEvery deployment begins read-only.
Your data
IsolatedNever pooled or commingled with another customer’s. Built in, not filtered.
Never trains a modelNot ours, not a provider’s; excluded by the inference terms.
Exportable, then deletableTake it out in full. On termination, it is deleted, not retained.
Encrypted in transit and at restBusiness fields encrypted again at the column level.
Your identity providerNo separate Velenza password to manage, or for us to lose.
The service dependencies underneath are shared under review rather than published. A public list of everything a platform runs on is a map for anyone probing it.
Acting on systems you do not own
A call to raise an invoice times out halfway through. Did it post? Fire it again and you may have billed a customer twice. Do nothing and you are silently short a real invoice. Velenza never lets that question stay open. Always exactly one of three outcomes:
CompletedFinished in full, verified. Never left half-done.
ReversedThe undo path was confirmed before the action ever ran.
Parked for a personNever a guess, never rounded to success.
These describe what Velenza can verify on its own side, never a claim about your vendor’s system. We won’t claim a record there cannot be altered. No platform honestly can.
Built to outlive the computers meant to break it
Data harvested today can be decrypted later, so the time to move is before the break. Velenza is post-quantum by default: the keys and signatures it controls use the NIST post-quantum standards wherever Google Cloud offers them in general availability. Where a capability is still in preview, it stays out of production. Nothing falls back to an old algorithm where a post-quantum path exists.
SignaturesEvery signature Velenza makes, on a receipt or a record, uses ML-DSA (FIPS 204) through Cloud KMS, generally available since 16 July 2026.
KeysKey establishment uses ML-KEM (FIPS 203) through Cloud KMS, generally available, with the hybrid form recommended by Google Cloud.
ConnectionsConnections Velenza terminates negotiate hybrid post-quantum key exchange (X25519MLKEM768) with every client that supports it.
PartnersA connection to a system you run uses post-quantum transport when that system supports it. When it does not, the connection is recorded exactly as negotiated and upgraded the day the partner can.
Checked against Google Cloud’s published availability on 15 October 2026. Quantum-safe key import is still in preview and is not claimed. As a capability moves from preview to general availability, it moves into production; never the other way round.
Models are wrong sometimes
Reasoning cannot cause an effectThe worst outcome of a wrong conclusion is a wrong proposal, held at a gate, reviewed by a person against the record. Not a wrong payment.
The evidence stays attachedA conclusion arrives with the records it was drawn from.
Velenza is built for that
Predictions are written down firstBefore the outcome exists, then graded when it does. The calls it got wrong stay on the page.
Every finding shows its sourcesThe only durable defense against a plausible-sounding wrong answer.
Accuracy figures belong to your deployment, measured on your data, against calls written down before their outcomes existed.
Send us your questionnaire
If you are assessing Velenza for someone else, send the standard questionnaire and we will work through it with you, control by control, against the architecture.
Brandon Meyer | Founder/CEO, Velenza BOC Inc
brandon@velenzaboc.com | www.velenzaboc.com
