Why the data layer comes first
Traditional software tries to fit many job roles into one predesigned interface. Axiomony separates the shared foundations from individual experiences. It is designed so a business expert can specify the real model and rules, and any employee can ask an AI assistant for the interface that helps them work.
- One schema: the organization’s real PostgreSQL tables, columns and relationships.
- One enforcement point: PostgreSQL decides what the authenticated role may read and write.
- Many experiences: different employees can design distinct forms, dashboards, reports and workflows.
Technical architecture
Data MCP
Fixed, parameterized tools read and write under each user’s PostgreSQL login. The MCP service has no shared superuser credentials. The database enforces GRANT, REVOKE, row-level security, constraints and triggers.
Administration MCP
Authorized administrators submit natural-language instructions. A server-side OpenAI model generates migration SQL based on the real catalog. The server stores a proposed plan in memory, returns the plan for review, and only applies it after explicit confirmation with implement_plan. SQL changes are made as real PostgreSQL objects, not in a parallel middleware rule engine.
Personal applications and hosting
Optional Nginx hosting stores static HTML/CSS/JS under each verified PostgreSQL user. Other users cannot modify those files through the MCP tools. This controls editing only; published pages are served publicly to visitors who can reach Nginx.
The current preferred data route is trusted runtime → Data MCP → PostgreSQL. A standalone static site cannot safely include PostgreSQL passwords. The authenticated server-side runtime needed for independent browser apps has not yet been built.
Security limitations
Not production-ready. The development prototype has not undergone a production security review or end-to-end Docker integration testing. Do not expose its Basic-auth MCP endpoint to the public internet.
| Area | Current behavior | Before production |
|---|---|---|
| Authentication | PostgreSQL username/password in HTTP Basic on each MCP request | HTTPS, OAuth/OIDC, secure sessions and brute-force controls |
| Authorization | PostgreSQL login; dynamic tool discovery; GRANT/RLS/column rules | Review for privilege escalation and policy gaps |
| AI-generated SQL | Static checks, plan review and manual confirmation | SQL AST validation, cloned-database tests, robust execution sandbox and durable audit |
| Site hosting | Nginx serves user-owned static files publicly | Domain/origin isolation, content abuse controls and secure data-backed app runtime |
| Integration tests | Node.js unit tests; no verified live Docker stack | Automated PostgreSQL/Nginx/MCP end-to-end tests |
| Plan storage | Short-lived in-process memory, lost on restart | Durable, auditable migration planning and approval |
Current status and next priorities
Axiomony v0.5.1 is an early-stage proof of concept. The current stack includes schema introspection, read/write operations, natural-language administration planning, role-aware tools and optional static publishing. A few next steps are especially important:
- Introduce public-client-compatible OAuth/OIDC authentication with secure, per-user PostgreSQL identity.
- Provide a trusted session-based runtime for user-created browser applications.
- Harden database migration execution with policy validation, test databases and durable audit trails.
- Run reproducible Docker integration tests across the MCP server, PostgreSQL and Nginx.
- Research MariaDB, MySQL Community, Microsoft SQL Server and Firebird as additional database backends. Require database-native read and write authorization rather than middleware-only checks. See the engine comparison and roadmap.
The GitHub repository contains the source code, configuration, unit tests and full README. This website documents the current prototype; it does not host the MCP service itself.