ZINFI URM ARCHITECTURE
One architecture. Every portal runs on it.
Every portal in this showcase — partner, sales and customer — is built the same way, on ZINFI's Unified Revenue Management (URM) architecture. Here's what each layer actually does.
Four layers, one boundary. The Experience layer — powered by Lovable — is what people touch, Connectivity carries data in and out, Orchestration holds the shared data and sequencing, and the Harness governs what any agent is allowed to do — all running on Microsoft AI Foundry. Add a portal and it inherits the whole stack; it does not rebuild it.
- Layer 01
- Experience
- Structured screens and forms for guided, repeatable workflows
- Layer 02
- Connectivity
- MCP — direct, structured tool and context exchange for AI agents themselves
- Layer 03
- Orchestration
- A shared data layer every portal reads from and writes to
- Layer 04
- Harness
- Agent action oversight — every action passes through the same governance, regardless of which layer triggered it
The Framework
One boundary around every layer, on Microsoft AI Foundry.
The whole architecture on one surface — Experience and Connectivity above, Orchestration underneath, all of it inside the Harness.
Lovable
ZINFIZINFI appears twice above — once as a connectivity channel, once as the orchestration engine underneath. Same platform, two different jobs.
How each layer works
Layer 01 · Experience
Experience
This is the layer people actually touch — powered by Lovable. Every screen, form, and conversation in a ZINFI portal is built and shipped here on Lovable.
- Structured screens and forms for guided, repeatable workflows
- Natural-language conversation for anything a form can't anticipate
- One design system across every portal — nothing feels bolted on
- Built and iterated in Lovable, prototype to production in the same codebase
- Consistent across every module — a partner never has to relearn the interface
The result: people work the system their own way — clicking through a form or just asking for what they need.
THE FRAMEWORK · Experience
LovableZINFILayer 02 · Connectivity
Connectivity
Nothing ZINFI builds lives in isolation. Three channels carry data in and out of every portal, each suited to a different kind of integration.
- MCP — direct, structured tool and context exchange for AI agents themselves
- Zapier — no-code automation across CRM, PRM, marketing and finance systems
- ZINFI — the native connector for ZINFI's own platform data
- No custom integration code required for any of the three channels
- New connections added in days, not engineering sprints
Whichever channel fits, the portal never has to build its own integration layer from scratch.
THE FRAMEWORK · Connectivity
LovableZINFILayer 03 · Orchestration
Orchestration
Underneath Experience and Connectivity, every portal draws on the same data and context — sequenced by one orchestration layer, never re-derived per portal.
- A shared data layer every portal reads from and writes to
- Context that persists across sessions, tools and portals
- Sequencing logic that decides what happens next, and in what order
- One source of truth — no portal re-derives its own copy of the data
- Consistent behavior across every portal built on the platform
This is what makes a dozen different-looking portals behave like one coherent platform instead of a dozen separate products.
THE FRAMEWORK · Orchestration
LovableZINFILayer 04 · Harness
Harness
Experience, Connectivity and Orchestration don't run loose. The Harness is the boundary that holds all three together — what's allowed to run, what's watched, what's stopped before it does damage.
- Agent action oversight — every action passes through the same governance, regardless of which layer triggered it
- Security enforced once, at the harness boundary — not reimplemented per portal
- Nothing crosses layers — or out to Foundry — without going through this boundary first
- Auditable by design — what ran, on whose behalf, and why
- Constrains before it acts — guardrails apply before an agent takes an action, not after
The difference between three components that happen to work together, and one system that's actually governed as a whole.
THE FRAMEWORK · Harness
LovableZINFIPlay with our synthetic data to learn.
Open the sandbox