Research index
R3Scoped case studyv0.1
INDRA Build-Log Case Study
A scoped proof of a 21-module business OS without exposing shared live data.
INDRA is architecturally promising, but the public demo is intentionally gated until demo data isolation and write guards are complete.
INDRA SuitePublished 2026-07-03Updated 2026-07-03
Abstract
This case study documents INDRA as a proof-of-concept business operating system: 21 modules across operations, finance, revenue, people, knowledge, intelligence, and workspace. The research value is the build log and architecture pattern, not a public shared-data demo. The public route is therefore request-based until a separate demo data source is provisioned.
Claims
- A business OS can be split into typed modules without turning every workflow into a disconnected SaaS island.
- RLS, ABAC, audit logging, and typed boundaries are non-negotiable before demo exposure.
- The correct next step is a pilot offer or isolated demo tenant, not a public writeable demo.
Methods
- Build and process review of the INDRA production app.
- Scope review against demo-data isolation, secrets rotation, and mutation guards.
- Product narrative mapping from modules to sellable pilot bundles.
Reproduce This
- Run the build against a non-production environment.
- Verify demo tenant separation before allowing public users.
- Confirm write paths are guarded by role and tenant policy.
Limitations
- This is a case study, not a benchmark.
- Public demo access remains blocked until tenant isolation is complete.