The VEERA Platform
A layered microservices architecture where every layer is shared, and every product adds to what the next one can use.
Five layers, one foundation
VEERA Framework
- Role
- The core is the foundation every product shares, whatever its industry: identity and access, tenants, notifications, audit, privacy, localization, documents and media, master data, billing and platform operations.
- How it connects
- Every layer above depends on the core, and the core depends on nothing above it. When it needs an external system — a payment gateway or a messaging provider, for example — it goes through the integration layer, so it stays independent of any single product or vendor.
- VEERA's role
- This is the heart of VEERA. The core is built once, secured once and audited once, then reused by every product. Multi-factor authentication, role-based access control and the audit trail live here, so every product has them from its first release.
Core Services
Every project starts with the VEERA core — configured, not rebuilt. For each project we configure the shared services it needs to its own tenants, roles and rules:
- User Service
- Authentication
- Authorization
- Notification
- Security
- Access Management
- Encryption
Services are plug & play. Each one runs independently and slots in beside the others, so a project switches on exactly what it needs today and adds more as it grows.
Everything — core and business services alike — is published through a single API Gateway, giving every client one secure, versioned entry point.
Business Services
VEERA Code Generator
Business logic is where a product is different — and where a startup needs speed. For this we use our own specialised tool, the VEERA Code Generator, built to create a startup's business services quickly.
We design the project's data model first. The Code Generator connects to that database, reads every entity and, driven by a professional configuration, generates all the main endpoints for each one — including full CRUD — ready to extend with the product's own rules.
The generated services follow the same standards as the rest of VEERA and are published through the same API Gateway, next to the core services.
- Data model
- VEERA Code Generator
- Endpoints
- API Gateway
Principles we build by
- Reuse first
- Every service is designed from day one so it can be promoted to the shared library.
- Lean by design
- We choose the simplest architecture that meets the need, and add complexity only when real usage demands it.
- Isolated integrations
- Each external system gets its own adapter, so third-party behaviour never leaks into the core.
- Designed for external failure
- When an external system is slow or unavailable, requests are queued and retried automatically. Users are never blocked.
- Audit from day one
- Every significant action is recorded in an audit trail from the first release, not retrofitted.
- Region-ready
- Arabic and right-to-left interfaces, local currencies and calendars, regional payment gateways and offline tolerance are part of the core.
Technical characteristics
- Microservices, independently deployable
- Containerized and orchestrated
- Event-driven, asynchronous messaging
- API-first, versioned APIs
- Multi-tenant by design, with scopes from global down to a single site
- Support for multiple database engines
Security built into the core
Multi-factor authentication across VEERA identity services.
Role-based access control with permissions per module and per site.
Audit trail of significant actions, searchable and exportable.
Privacy controls for consent, deletion requests and data retention.
Independently penetration-tested.
How VEERA is built
Why the platform is a set of small, independent services, and what that gives the products built on it.
Want the full architecture?
Detailed architecture and technology documentation is available to qualified partners under NDA.