Skip to content
RebellionTechGet Audit
Reference architectures

What we build, described the way an engineer would describe it

Six system archetypes covering most of what organisations actually ask for. Each one names the real problem, the part that is hard, and how every layer of the architecture answers it.

6
Archetypes
3
Complexity tiers
5
Layers each

A note on what this page is. RebellionTech is a new firm, so these are blueprints rather than delivered case studies — the architectures we are built to ship, described in full. We would rather show you exactly how we think than dress up a portfolio we have not earned yet. Client work will appear here under its own heading, with names and numbers, once it exists and once those clients agree to it.

Reference architectures

Six systems we build, opened up

These are blueprints, not case studies. Each one describes an archetype we are built to deliver: the real problem, the part that is genuinely hard, and how each layer of the architecture answers it.

Cross-system briefing engine

Executive Intelligence

Tier 3₹5,00,000 – ₹20,00,000+
The problem

Leadership needs answers that live across a CRM, a finance system, a ticketing tool and four years of documents. Today someone spends two days assembling each answer by hand, and it is stale by the time it lands.

The hard part

Entitlements and freshness. A briefing engine that shows a regional head another region’s numbers is a compliance incident, and one that quietly serves last quarter’s figures is worse than no engine at all. Both have to be structural, not prompted.

How the layers answer it
DataConnectors with incremental sync and per-source freshness SLAs. Every record carries its own as-of timestamp.
KnowledgeEntity resolution across systems so one customer is one entity. Ontology encodes the org’s own vocabulary for metrics.
ReasoningDecomposes a question into sub-queries, runs them against structured and unstructured sources, reconciles conflicts explicitly.
OrchestrationEntitlement filter applied at retrieval. Refusal path when a question crosses a boundary the asker cannot see.
InterfaceBriefings carry inline citations and an as-of line. Every number is clickable back to its source row.
Build this if
  • ✓Answers span 3+ systems
  • ✓Manual assembly takes days
  • ✓Strict access boundaries
  • ✓Numbers must be defensible
Do not build this if
✕A team of eight with everything already in one dashboard. Buy a BI tool.
Start here

Find out what you actually need
before you spend a rupee building it.

Send us the problem in whatever form you have it — a paragraph, a deck, a half-working prototype. You get a written architecture audit back in 72 hours.

A written read on what you are actually trying to build
The architecture we would use, and the two we rejected
Where this fails in production, and what that costs
A realistic budget range and timeline — or a reason not to start
Request the auditaurindesai@gmail.com

No discovery call required · No obligation · You keep the document either way