Agentic ERP

Xirag: An Agentic ERP AI Business Operating System

Run sales, contracts, signatures, scheduling, identity and payments on one core: one login, one directory and one audit trail across every module. Every workflow works for people on their own, and every module is designed so AI agents can operate it through permissioned actions.

  • BFSI
  • Education
  • Ecommerce
  • Logistics

Agents are not offered at launch; they are provided on request later.

Xirag · Acme Traders (demo)Early-access preview

Xirag CRM · Accounts

  • ATAcme Traders (demo)
  • KTKaveri Textiles (demo)
  • LFLotus Foods (demo)
  • Call12-minute call with Kiran (demo): wants an annual services contract
  • ContactKiran (demo) added as the accounts lead

Draft an annual services contract in CLM from this account.

Agent suggestion
Waiting for a person✓ Approved by Priya (demo), Sales

Xirag CLM · Contracts

Annual services agreement (demo)Acme Traders (demo)
  1. Approve
  2. Stamp
  3. Dispatch
  4. Sign
  5. Certify
Approver
Meera (demo), Legal
Obligation
Renewal notice: alert on the due date minus its notice period
Trail
Every stage written to the tamper-evident chain

Dispatch for signature to Kiran (demo) with Xirag eSign.

Agent suggestion
Waiting for a person✓ Approved by Meera (demo), Legal

Xirag eSign · Send for signature

  • KKiran (demo), Acme Traders (demo)Signed
  • PPriya (demo), counter-signerSigned
  • OTPStep-up passed before the document opened
  • PDFCertificate of Completion attached

Create a payment link for the first invoice.

Agent suggestion
Waiting for a person✓ Approved by Arjun (demo), Finance

Xirag Payments · Payment links

Payment linkSandbox

INR 1,20,000.00

Customer
Acme Traders (demo)
For
First invoice, annual services agreement (demo)
Status
Created
Event
payment_link.created

Book a follow-up with Kiran (demo) for next Wednesday.

Agent suggestion
Waiting for a person✓ Approved by Priya (demo), Sales

Xirag Calendar · Week

Week view: a kick-off on Monday, the follow-up call with Kiran (demo) on Wednesday and a renewal check-in on Thursday.

Done: five modules, one customer record, one audit trail.

Every step above also works by hand
Writing the audit entries✓ Every step is in the audit trail

Early-access preview: a scripted walk-through with fictional demo data. A person approves every step. Agents are not offered at launch; they are provided on request later.

  • 14 moduleson one core, from CRM to contracts
  • One loginXirag Account, or your own identity provider through Gate
  • One directorypeople and departments, shared by every module
  • One audit trailhash-chained, so a changed entry shows
Modules

14 agentic ERP modules on one core

Each module plugs into the same people, departments, records and audit trail, so nothing is set up twice. Every module is in development and open for early access.

Trust trace

Follow one approval from request to API event

A refund moves money out, so a second person always approves it, whatever an agent is allowed to do. Pick a step to inspect it. All data here is fictional.

The maker prepares the request

Anyone with the right membership can prepare a refund. Nothing moves until a second person approves it.

Action
Refund
Customer
Acme Traders (demo)
Amount
INR 2,400.00
Prepared by
Priya (demo), Support
Category
money-out: a person approves
Correlation ID
demo-acme-refund-01

A second person approves

The maker cannot approve their own request, and a high-risk approval asks for a fresh MFA challenge first. An agent may suggest a refund; it never approves one.

Checker
Arjun (demo), Finance
Step-up
Passed
Decision
Approved
Correlation ID
demo-acme-refund-01

The audit entry

Every durable change writes an entry with who, what, when, the before and after, and the correlation ID, linked by hash to the entry before it.

entity       refund (demo)
event        approved
actor        Arjun (demo), checker
maker        Priya (demo)
before       { "status": "pending_approval" }
after        { "status": "approved" }
correlation  demo-acme-refund-01
prev hash    computed below
hash         computed below

The API event

Your systems receive a versioned event that carries the same correlation ID, so one search finds the request, the approval, the audit entry and the event.

POST https://your-endpoint.example/webhooks
X-Correlation-Id: demo-acme-refund-01

{
  "type": "refund.created",
  "livemode": false,
  "...": "payload abbreviated (demo)"
}

Try to tamper with the chain

Three audit entries from different modules, each linked to the one before by a SHA-256 hash that your browser computes now. Change entry 2 and watch the chain catch it. A simplified illustration of how the audit chain works.

Industries

Shaped by your industry

A business receives Xirag according to its industry: the same core, with the workflows and words of that industry. Here is how Xirag is designed for each, using the modules above.

  • BFSI

    For payments businesses and insurers: maker-checker approvals on every money movement, contracts and signatures with a provable trail, and calling rules enforced on the server.

    • Payments
    • CLM
    • eSign
    • Dialer
  • Education

    For schools, colleges and universities: fee collection through Xirag Payments, terms and deadlines on a shared calendar, and one directory for staff and departments.

    • Payments
    • Calendar
    • Contacts
  • Ecommerce

    For online sellers: a storefront site with conversion tracking, checkout and refunds through Xirag Payments, and every customer conversation on one account timeline.

    • Website Builder
    • Payments
    • CRM
  • Logistics

    For carriers and logistics firms: partner contracts with obligation alerts, outbound calling campaigns, shared schedules, and payouts through Xirag Payments.

    • CLM
    • Dialer
    • Calendar
    • Payments
Xirag Payments

Xirag Payments for PAs and PGs

A payments technology stack that Xirag provides to payment aggregator (PA) and payment gateway (PG) companies: orders, methods, refunds, settlements, payouts, reconciliation, a developer platform and a console, built as a module of the Xirag operating system.

Built for trust

Controls designed in, not bolted on

Every module is designed and built to the same eight principles. They are design principles, not certifications. See them working in the Trust trace.

  • Audit trail

    Every durable change writes a hash-chained entry: who, what, when, before and after, and the correlation ID.

  • Maker-checker

    Where money moves or rules change, one person prepares and a second approves, with step-up for high-risk actions.

  • Least privilege

    People get access through memberships and roles. Agents act only within their seat's scopes, checked on the server.

  • Tenant isolation

    Every database access runs in the client's own tenant context, with row-level security keeping clients apart.

  • Encryption

    TLS 1.2 or later in transit; secrets and sensitive fields such as account numbers encrypted at rest.

  • Idempotent APIs

    Every create and state change takes an Idempotency-Key, so a retried request never runs twice.

  • Stable versions

    Breaking changes ship only in a new API version, with a migration guide and at least six months' notice.

  • Observability

    A correlation ID on every request, echoed in the response and carried across modules, end to end.

Early access

Run your business on Xirag

Every module is in development. Register for early access, or tell us about your business and what you need from an ERP.

Legal name
XIRAG PRIVATE LIMITED
Office
35/36 Station Border Road, Kodambakkam, Chennai 600024, Tamil Nadu
GSTIN
33AAACX6617K1Z6
Contact
admin@xirag.com