How it works

The shared kernel

Every product inherits the full platform stack. The product-specific code is a DSM plugin — typically 5,000–15,000 lines of EPL that implements the unique business logic. Everything else is inherited.

WHAT EVERY PRODUCT GETS FOR FREE (the 90%)
✓ EPL compiler (JIT, x64, ARM soon)
✓ Orion DB (hierarchical, transactional, AES-256)
✓ TProtocol (RSA + AES, multiplexed)
✓ User auth + sessions + permissions
✓ Organization + multi-tenant isolation
✓ HSRV (HTTP/HTTPS/WebSocket)
✓ GUI framework (90+ widgets)
✓ Thin client (WASM browser)
✓ Desktop app (Windows/macOS/Linux)
✓ Mobile wrapper (CEF + native voice)
✓ AI fleet (dispatch, billing, AIRecords)
✓ Plugin architecture (dynamic commands)
✓ Process supervisor (SrvOperation)
✓ File storage + versioning
✓ Real-time push (WebSocket)
✓ Stripe billing integration
Per-product breakdown

What each product adds (the 10%)

📊

BizOS Tables

PRODUCTION
From the kernel:

Orion DB partitions = tables. TT_Partition + DataColumns + DataItems = the entire table system. Views, filters, formulas — all operate on existing partition infrastructure. User permissions, org isolation, real-time sync — inherited from DSM.

Product-specific addition:

Column type system (30+ types: text, number, date, user, reference, formula, subtable). View rendering (list, board, calendar, Gantt). Data provider layer for dynamic schemas. Import/export (CSV). Marketplace app templates.

BizOS Mail

SHIPPING
From the kernel:

TProtocol handles all network I/O. Orion DB stores messages, folders, contacts, calendar events as partitions — same tree, same transactions. AI fleet classifies spam, auto-folders, executes actions. HSRV serves webmail. User auth, sessions, permissions — all inherited.

Product-specific addition:

SMTP inbound/outbound (RFC 5321). IMAP server (RFC 3501) with IDLE. MIME parsing. DKIM/SPF/DMARC. iMIP calendar invites. Plus-addressing. TMailPlugin DSM plugin (~15K lines).

💻

BizOS Code

SHIPPING
From the kernel:

Orion DB stores repos, branches, commits as tree nodes — file system capability used directly. TProtocol handles git smart HTTP transport. AI fleet does code review via MCP tools. User permissions map to git branch protection. Org isolation = repository ownership.

Product-specific addition:

Git pack protocol (upload-pack, receive-pack). Merge request system. Branch protection rules. Diff rendering. TGitHostPlugin DSM plugin. OrionGit streaming clone engine.

🏠

Elastcode Home

TESTING
From the kernel:

Orion DB partitions = shopping list, diet log, med schedule, budget, etc. — 17 partitions per user, all standard DSM partition/subtable infrastructure. AI fleet processes voice commands. Voice pipeline (Whisper + Piper) is a platform service. Mobile CEF wrapper is shared.

Product-specific addition:

Voice intent router (deterministic regex + AI fallback). Dashboard UI. Open Food Facts / USDA nutrition database integration. Proactive rules engine (AIActionRules). On-device Android STT/TTS. Wake word integration.

Spark

PRODUCTION
From the kernel:

AI fleet workers ARE Spark — they read the user's description, use MCP tools to create Tables partitions, define columns, insert data. The entire "app builder" is the AI fleet operating on the existing DSM infrastructure. Every generated app is just partitions + permissions.

Product-specific addition:

System prompt engineering. MCP tool registration for app creation verbs. App template marketplace. Build confirmation flow. Per-app billing.

🎨

Aurora

DEVELOPMENT
From the kernel:

EPL compiler with spatial math (vectors, matrices, ray-surface intersections — added to the language). TProtocol for distributed network rendering. GUI framework for the 3D viewport. The entire 120K→15K reduction comes from platform capabilities.

Product-specific addition:

Ray tracing core (BVH, photon mapping, adaptive sampling). Material/shader operator system. Scene graph. Camera system. ~15K lines of EPL. Read the full case study →

📁

BizOS Files

TESTING

Kernel: Orion DB file system capability — files ARE tree nodes. Versioning = partition history.
Added: UI for browsing, upload/download, sharing links, preview.

💬

BizOS Connect

TESTING

Kernel: WebSocket push = real-time messages. Orion DB partitions = channels. User system = members.
Added: Chat UI, threading, typing indicators, channel management.

📹

Watchcam

DEVELOPMENT

Kernel: V_Pipe video pipeline library (native C++, loaded by EPL). TProtocol streams video.
Added: Camera management, AI motion/person detection, alert system, recording.

The economics of reuse

Why this matters for investors

A traditional software company builds each product from scratch — separate team, separate stack, separate infrastructure. Each product costs $500K–$2M and 6–12 months.

We build each product as a DSM plugin — 5,000–15,000 lines of EPL that inherits the entire platform. The 10th product costs roughly the same as the 2nd. The marginal cost doesn't grow with the product count — it shrinks, because each new product exposes platform capabilities that benefit all others.

When we added spatial math for Aurora, every product got access to vector operations. When we built the AI fleet for Spark, every product got AI capabilities. When we built the mail server, every product got email sending. The platform compounds. The products multiply.