Technical architecture
Independent architecture Foundational design
PARANAVI® M does not depend on outside platforms. It is built in-house, from design to auth, payments, the policy engine, and the domain, as an independent architecture service.
Contents
PARANAVI® M technical architecture diagram

1A Single Source of Truth service
Starting from a single source of truth, each service extends only the attributes it needs. That is the structure we built
- One user ID based on unified auth
- Separate extension fields for each service
- Role-based permission branching
2Our own authentication and access control system
We avoid relying on outside auth SaaS and build security and access control in-house .
- Role-based access control (RBAC)
- Permission branching by service
- Revoked permissions take effect immediately
3Subscription and policy engine we designed
Going beyond a payment integration, this is an engine where we designed and built the subscription policy ourselves .
- Plan branching we designed
- Real-time usage calculation
- Korean payment module integration with internal state sync
4Domain-based Narrow A.I. design
Instead of generating general-purpose answers, it is a narrow AI that reflects the player's experience .
- A different path from general AGI
- Data specific to the startup domain
- Logic built around Socratic questions
Built-in-House Infrastructure
An independent system that turns experience from the startup field into a digital architecture.
Try it on the home screen