AppAxioms is Maigha’s shared platform for building and operating production SaaS: authenticated gateways, multi-tenant RBAC, domain microservices, observability, and control tooling— so each venture does not rebuild the spine that every serious product needs.
North star: One product, three layers, many small services. Gateways route. Services own logic. Ventures compound on the same foundation.
| Layer | Responsibility | Examples |
|---|---|---|
| Experience | Portals, landing, UX flows | Web dashboards, marketing site |
| Platform | Auth, routing, events, observability | FeMux, BeDemux, Redis, messaging |
| Domain | Bounded business capabilities | Appgen, Mailgen, Logger |
Each layer should start, deploy, and fail independently—so a studio can ship ventures without coupling every release to a monolith.
| Capability | Role |
|---|---|
| aasctl + Turborepo | Control plane for install, env sync, build, demux merge |
| Web / portal packages | RBAC dashboards, shared UI, auth client |
| Appgen | Application generation service and engine |
| Mailgen | Transactional and platform email |
| Logger | Centralized logging service |
| platform-env / service-core | Env profiles, shared middleware, errors, logging factories |
| Compose infra | Local and platform simulation (Mongo, Redis, RabbitMQ, …) |
Roles and permissions are first-class: platform admins, firm-scoped operators, and gated operations through demux config—not ad-hoc checks sprinkled in UI. That is how TaxInsights, MROS, and future ventures inherit a serious tenancy bar instead of inventing one per repo.
Studio leverage: Auth, routing, mail, logging, and ops tooling become platform compound interest—the unfair advantage behind faster, cleaner venture builds.
Product: AppAxioms — the platform layer for production SaaS.
Function: Gateway routing, multi-tenant RBAC, domain microservices, shared packages, and aasctl/Turborepo control.
Outcome: Ventures move faster on a spine built for international, production standards.