THE FIRST AND ONLY ERP BUILT FOR FEDERAL FINANCIAL DATA

Aegis ERP

Built from the ground up for federal financial data, with Super Intelligence (SI) built in at the core. Not a bloated legacy ERP retrofitted for government. Built to integrate with AcqBot.

LEGACY ERP VS AEGIS ERP

Built for federal financial data, not retrofitted to it

Federal financial management runs on legacy ERPs, and replacing them is hard. Moving off SAP or Oracle means more than loading opening balances: the legal and accounting history has to survive for later adjustments, payments, reconciliations and audits.

Legacy ERP
Aegis ERP
Data model
✕A commercial ledger, retrofitted for government accounts
✓Built from the ground up for federal financial data: TAS, fund, CLIN and ACRN on every distribution
Super Intelligence
✕Bolted on later, outside the controls
✓Built in at the core, bounded by the kernel. SI proposes and prepares; it never approves
Funds control
✕Checks layered on through customization
✓A deterministic kernel checks authority, approvals, funds and policy before anything posts
Policy
✕Customizations drift from current rules
✓Effective-dated, source-versioned policy, pinned on every posting
Rejections
✕Partial postings and manual cleanup
✓Posts atomically, or rejects with a reason code and no financial effect
Audit
✕Evidence reconstructed after the fact
✓Immutable journal and evidence that trace each posting to its command, approval and policy
Migration
✕History left behind in the old system
✓Legal and financial history carried over from SAP and Oracle, reconciled

HOW IT WORKS

Workflows ask. The kernel decides.

AEGIS AUTHORIZATION BOUNDARYby contractaskpostAcqBotacquisition dataSI agentspropose · prepare · routeWorkflowsrequisition → paymentKernelRust · deterministicauthority · funds · policyDECIDESPolicyeffective-datedJournal & evidencePostgreSQL · immutableReporting & closereports · assurance
The kernel decides
A deterministic Rust transaction and funds-control kernel checks authority, bound approvals, funds availability and accounting policy. It posts atomically, or rejects with a recorded reason and no financial effect.Select any box in the diagram to see what it does.

THE KERNEL DECIDES

Five things are settled before money moves

Each request must carry a valid authority and bound approvals before the kernel will consider it. Agents never approve their own actions.
AUTHORITY CHECKILLUSTRATIVE
Authority AUTH-0000valid
Approval by Sample Approverbound
Agent self-approvalnot allowed

ILLUSTRATIVE WALKTHROUGH

Watch a posting

Scroll through one sample request, from command to audit evidence. Records and amounts are illustrative.

01A requisition arrives
An AcqBot award becomes a RecordObligation command: an exact amount in cents, split across funding distributions, each pinned to its TAS, CLIN and ACRN.
02Authority and approvals
The kernel checks the approval bound to this exact command digest. A stale, revoked or self-approval is rejected with its reason code.
03Funds check
Each distribution is checked against appropriation and fund balances, under the effective-dated policy bundle the command pinned.
04Post, or reject cleanly
Every check passes, so the posting commits atomically to the ledger with its journal lines. A failure would record a reason code and no financial effect.
05Evidence, ready for audit
The obligation ledger and audit trail tie the posting to its command digest, approval and the policy actually used.
Requisition
Authority
Funds
Post
Evidence
Aegis ERP/ ObligationsILLUSTRATIVE
RecordObligation · CMD-0000-0142
command receivedUSD · exact cents
source.record_idAWD-0000-0031 (AcqBot)
accounting_date2027-01-14
amount_minor_units1250000 → $12,500.00
approval_idAPR-0000-0088
Distributions
DISTFUND · REVTAS / CLIN / ACRNAMOUNT
DIST-010100 · r7000-0000 / 0001 / AA$8,000.00
DIST-020200 · r3000-0001 / 0002 / AB$4,500.00
✓Distributions sum to the totalΣ = 1250000

KEY CAPABILITIES

What Aegis is built to do

Each capability closes only with tested acceptance evidence, not a specification.

0first-release acceptance groups
0dependency-ordered roadmap tasks
TARGET0 req/ssustained workload target
TARGET≤0 msp95 response target
FUND 0000 · samplecovered
availablecommittedobligated
Funds controlEvery posting is checked against available funds first.
JE-0000-0001appended
JE-0000-0002appended
JE-0000-0003appended
JE-0000-0004appended
JE-0000-0005appended
JE-0000-0006appended
JE-0000-0001appended
JE-0000-0002appended
JE-0000-0003appended
JE-0000-0004appended
JE-0000-0005appended
JE-0000-0006appended
Immutable journalRecords are appended, never edited.
v1v2v3
Effective-dated policyThe policy in force on the date applies.
Requisition→Receipt→Invoice→Payment
Procure-to-payRequisition to payment in one system.
SAP ECC
SAP S/4HANA
Oracle EBS
Oracle Fusion
Migration with reconciliationPlanned paths from SAP ECC, SAP S/4HANA, Oracle EBS and Oracle Fusion.
Proposeagent ✓
Prepareagent ✓
Approvehuman only 🔒
SI built in, boundedSI proposes and prepares. It never approves.
Counts and targets from the Aegis ERP first-release roadmap. Targets are design goals, not measured results. Example data in the cards is illustrative.

WHO IT IS FOR

Built for federal financial management

First-release scope covers funds control and posting, procure-to-pay, close, native reporting, migration from a legacy ERP, asset registration and depreciation, and reimbursable order creation.

Financial managers

Budget and funds-control officers who need to know every obligation and payment is authorized and funded.

Accounting and audit teams

Accountants, auditors and assurance reviewers who need evidence they can reproduce, not reconstruct.

Acquisition and payment offices

The offices whose requisitions, receipts, invoices and payments flow into the ledger, ideally straight from AcqBot.

Planning an ERP modernization?

If your organization is looking at its next financial system, we would like to hear from you.