Source before confidence
Every product surface should reveal where a state came from before asking a professional to act on it.
ComplyEaze is the operating story. Each product owns a different trust boundary.
Compliance products should tell you what they can prove.
Indian compliance work breaks when a notice, return, utility, and design harness all pretend to be the same product. Axal, Pack, Tools, and Sanchika now sit in one public map: what each does, where the data boundary lives, and what proof exists today.
The product family starts with operational evidence, not a decorative brand system.
- Authoritative design host
- sanchika.complyeaze.comStatic gallery deployed from Sanchika master.
- Public story surface
- complyeaze.comRoutes the family by job, boundary, and proof.
- Adoption rule
- Pilot firstContracts follow browser-tested surfaces, not taste alone.
Route by job. Then show the boundary before the action.
A unified story does not mean one visual costume for everything. It means the reader can see why Axal, Pack, Tools, and Sanchika exist together without confusing workspace custody, browser-local drafts, extension behavior, or design-system proof.
Practice operating systemAxalFirm workbenchTurns matters, obligations, evidence, clients, documents, and tasks into a reviewable desk for CA teams.Workspace-first, permission-aware, source-led compliance work.BoundaryAccount, workspace, roles, saved operational context.GST Portal evidence utilityPackGST evidence utilityKeeps the narrow filed-return collection job local, source-first, and separate from the full practice system.No-login public posture; no backend upload or telemetry claim.BoundaryBrowser extension, local artifact control, no custody claim.Browser-local draft benchToolsPublic utility benchCreates quick compliance review artifacts from pasted rows or plain text without needing an account.Utility surfaces stay browser-local until a deeper product lane exists.BoundaryBrowser-local drafts; no account, upload, or tenant state.Design harnessSanchikaEvidence loopDefines the trust and design brief loop before visual language spreads across the product family.Live gallery deploys from master, with smoke checks for stale public proof.BoundaryDesign contracts and static artifacts; no compliance truth.
Sanchika fits after the product truth is clear, not before it.
The design system should not manufacture confidence. It should make the right evidence, boundary, and next action legible enough that a CA team can trust the screen.
- 1A client, GSTIN, notice, return, or evidence request appears.
- 2The right product takes the job without hiding its boundary.
- 3A professional sees source, owner, status, evidence, and the safe next action.
- 4Sanchika captures the reusable pattern only after the rendered pilot works.
Boundaries stay visible
Pack remains local-first, Axal remains workspace-scoped, Tools stays browser-local, and Sanchika stays a harness.
Craft must be proven
The next design system step is rendered pilots with browser evidence, not a bigger pile of aspirational tokens.