ORM metamodel
Declarative models, typed fields, relations with explicit prefetch — no sneaky N+1.
The platform
A solid kernel. Zero hidden magic.
Kewos isn't a bag of modules: it's a coherent core providing ORM, security, events, jobs, multi-tenancy, i18n and a view engine — that business modules build on cleanly.
The core
What the kernel provides
The cross-cutting bricks every module reuses instead of reinventing.
Multi-level security
RBAC + record rules + field rules enforced in the ORM, deny by default, immutable audit.
Events & jobs
Transactional events and an idempotent job queue to decouple modules.
Multi-tenancy
One database per customer, systematic tenant resolution, no connection outside the resolver.
JSON view engine
Screens are declarative (JSON Schema + design tokens), rendered by a generic engine.
Controlled migrations
Versioned schema, never auto-created in prod; explicit, confirmed application.
By construction
Invariants, not promises
Security in the ORM
Permissions can't be bypassed via an endpoint: they live beneath the data layer.
Decimal everywhere
No float amounts; a (amount, currency, company amount) triple for every monetary value.
Extensible without forking
Runtime fields, automations and custom views — upgrade-safe.
Frequently asked
Is Kewos a fork of an existing ERP? +
No. Kewos is written from scratch with a clean architecture, to fix the structural weaknesses of legacy suites.
Can we extend without breaking upgrades? +
Yes: runtime fields, views and automations are declared by configuration and stay compatible across versions.
How is performance guaranteed? +
Explicit relation prefetch, controlled queries, profiling tests: no silent N+1 regression.
Ready to see Kewos on your use cases?
Book a demo, or estimate your SaaS and on-premise cost in two minutes.