QuantumHealth Innovations
AI for diagnostics and medical research.
• The control layer for AI agents
Let AI agents act. Keep humans in control.
Quantax sits between AI agents and your business systems. The Permission Firewall gives each agent short-lived access scoped to the step it's on. CommitLayer checks every high-risk action, from payments to deletions, against your rules, evidence and approvers before it's committed, and records every decision.
• Try it
An agent's change is held at CommitLayer. You decide whether it commits.
-
01
Propose
Agent: update supplier bank details for "Acme Supplies Ltd"
− payment_details •••• 4821 on file + payment_details •••• 9930 from invoiceEvidence: Invoice INV-2041
-
02
Check
Policy: sensitive field "payment_details" → independent verification required · amount threshold · approver authority
-
03
Decide
Paused · awaiting approval by Finance Controller
-
04
Record
Audit logged: decision, evidence, system state, hash
-
05
Recover
Rollback available where the connected system permits
You are the Finance Controller:
• The problem
Agents can now touch real systems. Every high-risk action needs a checkpoint.
01
Agents have left the chat window. They are moving into ERPs, databases, payment tools and SaaS apps, where a single write can delete records, move money or change a supplier.
02
Standing admin keys turn one mistake into many. An agent holding a broad, permanent key can cause mass deletions or an unauthorized transfer in seconds, before anyone notices.
03
Payment details are a known target. Supplier bank-detail changes are a well-known route for business email compromise fraud, and an agent reading a forged invoice can be fooled too.
04
Guardrails check words, not changes. Existing tools inspect prompts and outputs. None look at the access an agent holds or the actual change about to be committed to your systems.
• The Quantax platform
Permission Firewall controls what an agent can reach. CommitLayer controls what it can commit.
Two controls around every high-risk agent action: payments, deletions, transfers and record changes.
BEFORE THE ACTION
Permission Firewall
Instead of a fixed admin key, each agent gets short-lived, step-by-step permissions scoped to what it is doing right now. Access expires when the step ends.
Scoped, just-in-time permission
In development
AT COMMIT
CommitLayer
Every high-risk change is checked against your rules and evidence, paused for a human where it matters, recorded, and recoverable.
Evidence · policy · human approval · audit · rollback
In development
• Speed and control
Routine work stays fast. Sensitive changes get a checkpoint.
Agents keep coding invoices, matching receipts and drafting vendor updates at machine speed. CommitLayer only steps in when a change touches something your controls care about.
| Agent change | Rule | Outcome |
|---|---|---|
| Code invoice INV-2038 to 6100 | Within policy | Allowed |
| Update supplier contact email | Low-risk field | Allowed |
| Change payment_details | Sensitive field | Paused |
| Approve INV-2044 above threshold | Approver authority | Paused |
| Release payment run | Money movement | Human only |
• How it works
Six steps around every sensitive change.
- 01
Propose
The agent submits the change it wants to make, with the evidence behind it.
- 02
Check
CommitLayer tests the change against your policies, fields, thresholds and authority.
- 03
Decide
Allow · pause for a named approver · block.
- 04
Record
Every decision lands in a tamper-evident audit trail.
- 05
Recover
Reversal or compensating steps when something needs undoing.
- 06
Govern live
Policies are versioned, reviewed and reported on, like any other control.
• Architecture
Two controls between agents and the systems of record.
01 · SOURCE
AI agent
↓ requests a step
02 · ACCESS
Permission Firewall
↓ grant + change
03 · COMMIT
Quantax CommitLayer
↓ commit
04 · SYSTEMS
Business systems
• First workflow
Supplier and invoice changes in finance operations.
We start where the risk is concrete and the controls are well understood: the vendor master and the invoice approval chain.
Next: any system where an agent's mistake is expensive.
| Action | CommitLayer requires |
|---|---|
| Prepare supplier-record update | Agent may propose |
| Change payment details | Independent verification |
| Approve invoice above threshold | Named approver |
| Release money | Human approval, always |
• Design principle
0 payments moved without a human.
A rule we build to, not a metric we report. Four commitments follow from it.
No autonomous money movement
CommitLayer never releases funds on an agent's say-so. Money moves only after a human approves it.
Details →Workflow-aware, not generic guardrails
Rules are written in finance terms: fields, thresholds, segregation of duties and approver authority.
Details →Audit by default
Every proposal, check and decision is recorded with its evidence, whether it was allowed, paused or blocked.
Details →Security first, least-privilege
The Permission Firewall gives each agent only the access its current step needs, and takes it back when the step ends.
Details →- OCT 2026
quantax.space launched; design-partner program opened
- MAY 2026
CommitLayer prototype: supplier and invoice change workflow (propose → check → decide → record → recover)
- DEC 2025
Research began on AI-agent safety: permissions, approvals and audit for agents acting in real business systems
- 2025
Company incorporated (Delaware)
• Design partners
Help shape the first pilot: one agent, one accounting or ERP workflow, your rules.
We work closely with a small number of finance teams to define policies, test the approval flow and agree what good looks like before anything touches production.
• The Quantax platform
Control what an agent can reach, and what it can commit.
Quantax is the control layer for AI agents. The Permission Firewall scopes each agent's access to the step it's on. CommitLayer decides, change by change, whether a write goes through, waits for a person, or stops, and keeps the record that proves it. Neither replaces your agents or your systems.
In development · private design-partner pilots
• Permission Firewall · before the action
No standing admin keys. Just-in-time access, one step at a time.
Instead of a fixed admin key, each agent gets short-lived, step-by-step permissions scoped to what it is doing right now. Access expires when the step ends, so a confused or compromised agent can't reach beyond its current task.
Just-in-time grants
Access is issued when a step starts, never held in advance.
Step-scoped
Each grant covers only the records and actions the current step needs.
Auto-expiring
Access ends with the step. Nothing is left standing for the next mistake.
Least privilege
The narrowest access that gets the job done, by default.
Every grant logged
Who asked, what was granted, for which step, and when it expired.
• CommitLayer · at commit
Evidence, policy, human approval, audit and rollback for every high-risk change.
• The lifecycle
Six steps, in detail.
01 · PROPOSE
The agent sends the exact change it intends: the record, the field, the old and new value, and the evidence it relied on, such as an invoice or an email.
02 · CHECK
The policy engine evaluates the change against your rules: is the field sensitive, is the amount above threshold, who may approve it, and is the evidence sufficient and independent?
03 · DECIDE
One of three outcomes: allow, pause for a named approver, or block. Approvers see the change, the evidence and the rule that triggered the pause in one view.
04 · RECORD
The proposal, checks, decision, approver and resulting system state are written to a tamper-evident log, each entry hashed and chained to the one before it.
05 · RECOVER
Where the connected system permits, a committed change can be reversed; where it doesn't, CommitLayer records the compensating steps to take.
06 · GOVERN
Policies are versioned and reviewed like any other control, with reports showing what agents proposed and how each change was handled.
• Policy types
Rules written the way finance already thinks.
| Policy | What it does |
|---|---|
| Sensitive fields | Flags changes to fields such as payment details, tax IDs or remittance addresses. |
| Amount thresholds | Routes anything above a set value to a person, by entity, currency or vendor. |
| Segregation of duties | Stops the same actor, human or agent, from proposing and approving one change. |
| Approver authority | Matches each pause to someone with the authority to approve it. |
| Evidence requirements | Requires supporting documents, and independent verification where the risk calls for it. |
• Outcomes
Three possible decisions. Nothing in between.
ALLOW
Within policy
The change is committed straight away and logged. Routine work isn't slowed down.
PAUSE
Wait for a named approver
The change is held until the right person approves or rejects it, with full context.
BLOCK
Outside policy
The change is refused, the agent is told why, and the attempt is recorded.
• Audit trail
What every entry holds.
Each record is hashed and chained, so a missing or altered entry is detectable. Exports are designed for auditors, not just engineers.
proposal agent, record, field, old → new
evidence documents and sources cited
checks policies evaluated + version
decision allow · pause · block
approver name, role, timestamp
state system state before and after
hash chained to the previous entry
• Recovery
When something needs undoing, the path is already written down.
Because CommitLayer records the state before each change, it can offer a reversal where the connected system supports one.
Where reversal isn't possible, for example after a payment file has left the building, it lists the compensating steps and who owns them. We are explicit about which is which.
• Who it's for
Finance operations teams
Controllers and AP leads who want agent productivity without loosening controls.
Companies deploying AI agents
Teams putting agents into real systems who need approvals and an audit trail from day one.
AI-agent builders
Builders who want their agents to pass a customer's security and finance review.
• FAQ
Common questions.
How is this different from an API key?
Keys are standing and broad; grants are per-step and expire. A Permission Firewall grant covers one step of one task, and is logged when it's issued and when it ends.
Is it only for finance?
No. Finance operations is the first workflow. Quantax covers any high-risk agent action, such as payments, deletions, transfers and record changes.
Does CommitLayer move money?
No. CommitLayer never releases funds. Money movement always requires human approval in your own systems.
Does it replace my ERP approvals?
No. It adds an agent-aware checkpoint in front of them. Your existing approval workflows stay in place.
Which systems does it connect to?
Integration details are shared privately with design partners.
Is it available?
Permission Firewall and CommitLayer are in development, with private design-partner pilots now. It is not yet publicly available.
How is data handled?
Least-privilege access, encrypted in transit and at rest. See Security for details.
• Security & trust
Private, auditable, in your control.
A product that checks other software's changes has to hold itself to a higher bar. These are the practices we follow today, in plain words.
• Practices
Least-privilege access
Every integration and every team member gets the narrowest access the job needs. Write access is scoped per workflow.
IN PLACEEncryption in transit and at rest
Traffic uses TLS. Stored data is encrypted at rest.
IN PLACETamper-evident audit logs
Decisions are hashed and chained, so a removed or edited entry can be detected.
BY DESIGNHuman approval for money movement
No agent, and no CommitLayer rule, can release funds without a person approving it.
BY DESIGNData minimisation
We collect only what a decision needs and mask sensitive values, such as bank details, wherever we can.
BY DESIGNAccess reviews
Access to systems and data is reviewed regularly and removed when no longer needed.
IN PLACEResponsible disclosure
Found a vulnerability? Report it to us privately and give us reasonable time to fix it before disclosure. We won't pursue good-faith research.
• Compliance roadmap
Stated honestly.
"We are preparing for SOC 2. We'll publish status here when an audit is underway."
We don't display badges we haven't earned. Design partners can request our security overview and a DPA under NDA.
• About Quantax
We build the controls that let AI agents do real work.
Quantax is the control layer for AI agents: the Permission Firewall scopes what an agent can reach, and CommitLayer controls what it can commit. Finance operations is our first workflow, where a wrong change costs real money and the controls are well understood.
• Mission
To make it safe for companies to let AI agents act on their systems, with every consequential change checked, approved by the right person, recorded and reversible.
• Leadership
Leadership.
Sachin Kudari
Founder & CEO
• Company facts
For reviewers and partners.
| Fact | Detail |
|---|---|
| Parent company | UnitedQuantumX Inc. |
| Entity | Delaware C-Corporation |
| Founded | 2025 |
| Funding | Bootstrapped |
| Focus | Applied AI safety for agents |
| Registered address | 254 Chapman Rd, Ste 208 #22419, Newark, Delaware 19702, United States |
• Parent company
UnitedQuantumX initiatives.
UnitedQuantumX Inc. is a research-first holding company working across AI and quantum. Quantax is its applied-AI company and the first to ship a product.
Research stage
QuantumShield Technologies
Quantum-safe security.
QuantumFin Analytics
AI analytics and risk models.
QuantumCore Technologies
Quantum computing and algorithms.
QuantumMind Systems
Decision intelligence.
QuantumLex Solutions
AI for legal research and compliance.
QuantumConnect Solutions
Secure, resilient networking.
QuantumGenix Solutions
Computational biology and genomics AI.
QuantumFrontier Labs
Long-range research, including fusion energy.
• Changelog
Changelog.
Real milestones only, newest first.
- OCT 2026
quantax.space launched; design-partner program opened
Our public site went live, and we began accepting a small number of teams to shape the first pilot around one agent and one workflow.
- MAY 2026
CommitLayer prototype: supplier and invoice change workflow (propose → check → decide → record → recover)
The first working prototype runs supplier and invoice changes through policy checks and a named approver, recording every decision.
- DEC 2025
Research began on AI-agent safety: permissions, approvals and audit for agents acting in real business systems
We started studying how to give agents only the access they need and keep a person in the loop for consequential changes.
- 2025
Company incorporated (Delaware)
Incorporated as a Delaware C-Corporation, focused on research across AI and quantum.
• Careers
We're a small founding team.
We aren't listing open roles yet. If you're an exceptional engineer interested in AI safety, finance systems or agent infrastructure, we'd still like to hear from you.
01
AI safety
Policy engines, evaluation and controls for systems that act.
02
Finance systems
ERPs, accounting platforms, vendor masters and the controls around them.
03
Agent infrastructure
Audit logs, approvals and recovery that hold up in production.
• Status
All systems operational
Website
OperationalContact
OperationalCommitLayer
Private pilot — not publicly available• Legal
Privacy policy
Effective October 2026
This policy explains how UnitedQuantumX Inc. ("we", "us"), which operates Quantax, handles personal information on quantax.space (the "site").
What we collect
- Information you send us. If you contact us by email, we receive your name, email address and anything you choose to include.
- Basic technical data. Our hosting provider may log standard request data, such as IP address, browser type and pages requested, to keep the site secure and running.
Cookies and tracking
The site uses no tracking or advertising cookies and no third-party analytics. If you choose a light or dark theme, that preference is stored in your browser only.
How we use information
To reply to you, evaluate design-partner and job enquiries, keep the site secure, and meet legal obligations. We do not sell personal information.
Sharing
We share information only with service providers who help us run the site and email, under confidentiality obligations, or where the law requires it.
Retention
We keep correspondence only as long as needed for the purpose it was sent, or as the law requires.
Your choices
You can ask to access, correct or delete personal information we hold about you. We will respond within a reasonable time.
Changes
We'll post any updates on this page with a new effective date.
Contact
Reach us with the . UnitedQuantumX Inc., 254 Chapman Rd, Ste 208 #22419, Newark, Delaware 19702, United States.
• Legal
Website terms of use
Effective October 2026
These terms govern your use of quantax.space, operated by UnitedQuantumX Inc. on behalf of Quantax. By using the site you agree to them.
Information only
The site describes CommitLayer, which is in development and not yet publicly available. Nothing here is an offer to sell or a commitment to deliver any feature. Examples and demo data are illustrative.
Acceptable use
- Don't attempt to disrupt, overload or gain unauthorised access to the site or our systems.
- Don't scrape the site at volume or use it to send spam or malicious content.
- Security research is welcome under our responsible disclosure practice on the Security page.
Intellectual property
The site's content, the Quantax and CommitLayer names and the site design belong to UnitedQuantumX Inc. You may link to the site and share its pages for non-commercial reference.
Third-party links
Links to other sites are provided for convenience. We aren't responsible for their content.
No warranty; limitation of liability
The site is provided "as is" without warranties of any kind. To the extent the law allows, UnitedQuantumX Inc. is not liable for any indirect or consequential loss arising from your use of the site.
Governing law
These terms are governed by the laws of the State of Delaware, United States.
Changes and contact
We may update these terms and will post the new effective date here. Questions? Use the .