now-ist · easy · secure

The technology infrastructure that accelerates every team building software.

NOVEXA Business is a production-grade .NET platform that companies, institutions, startups and product teams adopt instead of rebuilding their operational core. Party-centric data model, Orleans actor runtime, CQRS, and a delivery pipeline already proven under load — transferred to you, not written from zero.

.NET Orleans CQRS PostgreSQL Kubernetes OpenAPI
Sample(CRM) solution explorer
NOVEXA.CRM.API → REST · Webhooks · Mobile
NOVEXA.CRM.WebComponents → Blazor
NOVEXA.CRM.SharedKernel → IGrain contracts
NOVEXA.CRM.Silo → Grains · Jobs · Specs
NOVEXA.CRM.InfraStructure → Data · Seed · Integration
Novexa.Gateway → ERP · finance · 3rd-party
Novexa.Admin → claims · screen rights
90%+
Enforced code-coverage floor across aggregate roots
80%
Database load removed by Orleans grain-resident cache
4
Isolated data stores — OTP, identity, health, runtime
1
Party-centric core model every entity resolves to
01 — What it is

An accelerator, not another framework.

Technology transfer removes the months a venture normally spends on operational infrastructure before it can ship anything a customer sees.

The cost you are actually paying

Every team that builds a product first builds the same substrate: identity, parties and organisations, relationships, contact mechanisms, permissions, notifications, reporting, integration, deployment. It is a year of senior engineering that differentiates nothing.


What NOVEXA transfers

A running .NET platform with the substrate already designed, tested, documented and deployed — reference architecture, universal data model, actor-based runtime, CI/CD, monitoring and support. Your team starts at domain logic on day one.


Who it is for

Enterprises modernising an operational core, institutions with audit and authority requirements, startups that need credibility on day one, and integrators delivering client platforms on a foundation they did not have to underwrite.

02 — Architecture

Layered, actor-driven, party-centric.

Front-end surfaces speak to one API layer. Orleans carries state and concurrency. Every entity in the domain resolves back to a single Party table.

Front end
REST APIs
Webhooks
Mobile apps
NOVEXA.CRM.API
Web apps · Blazor Server
NOVEXA.CRM.WebComponents
.NET Orleans ↕
NOVEXA.CRM.SharedKernel
Back end
Specifications
Jobs
Grains
NOVEXA.CRM.Silo
Data access
Seed
Integration
NOVEXA.CRM.InfraStructure
Party Person Organization Relationship ContactMechanism IdentityCard Lead Portfolio Acquisition Asset Classification CommunicationEvent Note
Universal domain model — star topology on Party
Data model
Star topology on Party
Person and Organization derive from Party; every operational record links back to it directly or indirectly, so identity and integrity hold at one point.
Runtime
Single-thread actors
Grains hold their own state and run single-threaded by nature — complex workflows split across actors without RabbitMQ or a separate queue tier.
Read / write
CQRS separation
Queries and commands are handled in separate layers, which is what makes the read path cheap to scale independently of the write path.
03 — Platform

Stack, modules, integration surface.

Technology & tools

Backend
ASP.NET Core · Entity Framework · .NET Orleans · .NET Aspire
Frontend
Blazor Server
Data
PostgreSQL · Redis cache · pgvector search
API
RESTful · Swagger / OpenAPI documentation
DevOps
Docker · GitHub Actions CI/CD · Kubernetes (optional)
Quality
MsTest · SonarQube · Code Analyzers

Modules & layers

01
Party, person & organisation management
Every counterparty managed from one centre; flexible structure through Person and Organization types derived from Party, with identity data, roles and relationships held in detail.
02
Operational CRM
Relationships between people and companies — customer, supplier, dealer — tracked centrally, with contact mechanisms, identity and portfolio unified per party and history separated from live state.
03
Customer lifecycle
Lead through conversion and post-sale: the whole process is observable, with lifecycle stages recorded against the party.
04
Reporting & dashboards
Instant and historical reports across every process, with per-user summary and detail views as a decision-support layer.
05
Notification & integration
Event-driven notifications by e-mail, SMS and push, plus integration capability with ERP, payment services and third-party APIs.
06
CQRS read/write split
Query and command paths handled in separate layers — the architectural precondition for high performance and independent scaling.

Integrations & API

API classes are generated for every IGrain interface inside the SharedKernel and exposed as functional REST endpoints that respect domain logic.

Gateway

Novexa.Gateway centralises log and trace, manages runtime configuration and provides a flexible, modular integration substrate.

Documentation

Swagger / OpenAPI for every endpoint, so integrators can test and progress against standards without a discovery call.

Onboarding

Each integration ships with technical documentation and sample files containing example API calls.

04 — Developer Program

Work inside the platform before you commit to it.

A structured path for engineers who want hands-on time with the architecture, the codebase and the team that built it — before any commercial conversation starts.

01
Architecture onboarding
A guided walkthrough of the Party-centric model, the Orleans runtime and the CQRS split — the mental model before the code.
02
Sandbox + sample solution
A running environment and the CRM sample solution to explore, break and rebuild — not slides, an actual codebase.
03
Code review with the core team
Submit real changes and get them reviewed directly by the engineers who own the architecture — the same standard production pull requests meet.
04
Contribution & delivery track
Contributors who show fit move onto paid delivery work or a transfer engagement — this is a path in, not a one-off exercise.

Apply to the program

Tell us where you're coming from and what you want to work on — an architect reviews every application.

05 — Assurance

Built to survive procurement.

Security, scale, code quality and delivery are properties of the platform, not promises added later in a questionnaire.

Security & data

Container-based authentication
Claims — authority and identity — are attached automatically to every request at sign-in.
Screen & query rights
Novexa.Admin loads per-user rights into the container; menus, pages, tabs and buttons are each checked independently. Query scope narrows data to own customers, linked staff, or a shared portfolio.
Four isolated databases
Separate stores for OTP, user and authority data (encrypted), health checks and the Orleans substrate. No direct access to the OLTP database.
Audit trail & PageHit
Every operation is recorded with acting user identity and timestamp; each first page render logs a PageHit with user, timestamp and URL.

Performance & scalability

Grain-resident cache
Each write is handled in a dedicated Grain class that keeps updated data in its own cache — removing up to 80% of database load and the GetById round-trip on every query.
Async without a queue tier
Because actors are single-threaded by nature, asynchronous work is split across actors — no RabbitMQ or comparable service required in the substrate.
Horizontal & vertical scale
Kubernetes deployment options suited to microservice topology give high availability and elasticity in both directions.
Vector search over large data
PostgreSQL vector search gives very fast keyword access across large datasets.

Code quality & standards

Coverage floor of 90%
MsTest covers all aggregate roots and their functions at unit and integration level; coverage is not allowed to fall below 90%.
SonarQube gate
High Quality Gate and maintainability ratings with low technical debt, reported continuously.
Review before merge
All changes go through GitHub pull requests; nothing merges to main without approval.
SOLID, clean code, analyzers
Code Analyzers prevent developers from stepping outside the standard, and complexity is actively managed.

DevOps & delivery

Automated build & deploy
GitHub Actions tests every change through the pipeline and deploys it to the appropriate environment.
Monitoring & logging
Aspire Dashboard for service state and metrics, Orleans Dashboard for actor and grain performance, HealthCheck UI for dependency health, and instant alerts on critical operations.
Automatic rollback
Any failed deploy returns the system to the previous release without intervention.
Daily backup
All data and critical components are backed up automatically every day, with tested restore paths.
06 — In use

Three scenarios, end to end.

Scenario 01

New customer & customer card

  • User adds a customer; the record is written to Party as a Person or Organization.
  • Contact, identity, relationship and portfolio detail are entered on the customer card.
  • Notes, documents and relationship definitions are handled from that same card.
Scenario 02

Lead to lifecycle

  • A lead is created and associated with a Party — created if it does not yet exist.
  • Conversion and lifecycle stage — cold, warm, active — are recorded as a distinct process.
  • Every step is followed from the dashboard.
Scenario 03

Customer list by time & authority

  • The list a user sees is bounded by their rights.
  • Scope is limited to the portfolio that user can reach.
  • Filter and search operate within the time and authority frame.
07 — Roadmap

Where the platform goes next.

Near term
Mobile application integration
The existing CRM infrastructure carried onto mobile platforms with access and tracking from mobile devices.
Advanced reporting
Analytic and customisable report screens, user-specific dashboards and deeper data visualisation.
Long term
AI-assisted automation
Automatic customer segmentation, predictive sales and opportunity management, and intelligent recommendation systems.
Wider integration surface
Broader integration with external systems and services — ERP, accounting, communication platforms, social channels.
08 — Engagement

Three ways to take it on.

Commercial terms are set per engagement against scope, environment count and support level.

09 — Team

The two people accountable for it.

Emre COSKUN

Emre COSKUN

Founder · Software Architect · CTO
Muzaffer Demirhan KESKIN

Muzaffer Demirhan KESKIN

Founder · Strategy & Marketing
10 — NXDEV.Blog

Where we write about the platform, in public.

For developers For fintech For founders
—Architecture notes from the team that runs the platform, not marketing copy about it.
—Deep dives into the Party model, Orleans grains and the CQRS trade-offs — including what we'd do differently today.
—Field notes from real engagements — what broke, what scaled, what procurement actually asked for.
—A running log of the roadmap, written as we build it rather than after the fact.
NXDEV.Blog

Published separately from novexabusiness.com so it can move at engineering speed.

Read NXDEV.Blog
11 — Access

Tell us what you're building.

An architect reads every submission. You'll get a written response on fit, a suggested engagement model, and a technical walkthrough if it makes sense.

—Response within two business days
—Technical documentation on request under NDA
—Investor materials available separately
You
Company
Your need