Engineering
How we build
Prabhix is a company that ships products. This page is about the engineering practices behind them — not a claim that one console is the whole business.
Practices
What every Prabhix product inherits
One identity, many products
Customers sign in once through Prabhix Identity. Each product — OneOps, MobiStack, and what comes next — is a client of that provider, not its own login silo.
Tenant isolation by default
Organization-scoped data at every layer: JWT claims, request filters, ORM filters, and Postgres row-level security on high-risk tables.
Automation over busywork
Outbox workers, webhook-driven entitlements, and rule-based routing so teams spend time on decisions, not handoffs.
Modular monoliths
Clear module boundaries inside a deployable unit — auth, org, mail, billing, audit — so we move fast without losing operational clarity.
Designed to scale
Cursor pagination, Redis caches, SKIP LOCKED workers, and partitioned hot paths when a single organization grows large.
Product-shaped experiences
Shared foundations do not mean a generic UI. Each product owns its workflows, mobile apps, and domain language.
Products
Architecture lives with the product
Module maps, inbox pipelines, and repair-shop workflows belong on product pages — not as a company-wide “platform” pitch.
Stack
A short technical snapshot
- APIs — Spring Boot modular services with clear domain modules
- Data — PostgreSQL with tenant scoping; Redis for cache and fan-out
- Web — Next.js marketing and product SPAs with shared design tokens
- Mobile — Offline-first apps where the field work demands it
- Identity — Central OIDC provider for first-party products
- Billing — Razorpay subscriptions and GST-aware invoicing where sold
Want a walkthrough?
Book a session focused on the product that fits your team — OneOps, MobiStack, or a custom build.