Products pull the platform
A capability enters Twillx only when a live product needs it now and a second product will need it next.
TheFabricOfFutureEngineering.
At Virtuos, We're Reimagining How Software Is Engineered For An AI-First World. Twillx Brings Core, Fabric, Runtime And Studio Together Into One Unified Ecosystem, So Engineers Create Faster, Build Smarter And Innovate Without Boundaries.
Components, plus the method
0+0
Modules, one ID each
0
Stage engineering lifecycle
0
Products, one foundation
∞
The Vision
A twill is a weave: threads cross over and under to make fabric that is stronger than any single thread. Twillx does the same for software. Every product we build adds threads to a shared foundation, and every new product starts stronger than the last.
Harvest, don't invent
We start from what working products have already proved: connectors, intake, agent triage and drafting.
Boring where it matters
Open source, two languages, one database, one cloud. We save the novelty for agents and experience.
The rule of two
Code moves into the shared foundation when a second product needs it. Until then it stays in the product.
One Foundation.
Five Components.
Each Component Has One Job. Products Sit On Top And Pull. Fabric Connects And Orchestrates. Core And Runtime Keep Everything Secure And Running. The Method Governs How It All Gets Built.
Twillx Core · 13 modules
Twillx Core
The engineering DNA.
Tenancy, identity and policy, done once and done right. Retrofitting these later is the most expensive mistake a platform can make, so they go in first.
- CORE-TEN
- CORE-IAM
- CORE-AUTHZ
- CORE-SEC
- CORE-AUD
- CORE-SCH
- CORE-SDK
Born From Twillx.
Each product builds only its own domain, its signature experience and its own agents. Everything else, from identity to agents to observability, is woven in from Twillx.
XODY SIMS
Agentic omnichannel messaging
Agents triage, route and draft replies to inbound messages in your brand voice, and humans approve before anything is sent. SIMS proves every Fabric module first.
Signature build
Omnichannel inbox · multilingual drafts
October.ai
Agentic service flows
Service requests run as durable workflows with SLA clocks, approvals and escalations, built on Twillx Fabric.
Signature build
Service catalog · SLAs · portal builder
Dhoom.ai
AI-native marketing
Journeys designed on the flow canvas, creative produced with agents, and campaign sign-off kept with humans.
Signature build
Journeys · creative studio · attribution
XODY CRM
The AI-code CRM
Admins describe a change in plain language, and Twillx agents write typed, tested code against the XODY SDK. AI code takes the place of low-code.
Signature build
AI-code customisation · pipeline
Platform down.
Harvest up.
A small Twillx platform team serves product teams. Templates, skills and modules flow down to products. Proven product code is harvested back into Twillx when a second product needs it.
Product teams
+ AI agents
< templatesharvest >
Twillx platform
Core · Fabric · Runtime · Studio
Also built on Twillx: Virtuos consulting engagements, which ship faster for clients on the same foundation.
| Extension point | SIMS | October | Dhoom | XODY CRM |
|---|---|---|---|---|
| Connectors | ||||
| Domain objects | ||||
| Agents & tools | ||||
| Workflows | ||||
| UX | ||||
| Data & insight |
Relies on it heavilyUses it
Twillx provides the extension point, and each product adds its own domain.
How Work Moves
Through Twillx.
Requests, agents and engineers' changes all travel the same paved paths. Tenant context is set once and goes everywhere the work goes.
A request, end to end
Every product request takes this path. Tenant context is set once at the edge and travels with the request.
App shell
STU-SHLSigned in through SSO, with the tenant selected
API gateway
CORE-APIResolves the tenant, applies rate limits and tags the request
Identity
CORE-IAMValidates the user, agent or service identity
Authorisation
CORE-AUTHZOne check: may this subject do this action on this record?
Product service
CORE-DATReads and writes through the tenant data layer, with RLS enforcing isolation
Workflow
FAB-WFAnything long-running or awaiting approval becomes durable
Agent + model
FAB-AGTCalls tools through MCP and models through the gateway, within budget
Record everything
CORE-AUDAudit, event, trace and metering
The Twillx Method:
Engineer Forwardly.
Seven Stages, Four Gates And Three Risk Tiers. At Every Stage AI Writes The First Draft And A Named Human Signs It Off, And Every Release Leaves Reusable Assets For The Next.
Evolve feeds intent
The Forwardly
Loop
T0
Low risk
Docs, tests, UI components, internal tools.
CI green and one reviewer → ships directly
T1
Product change
Features, connectors, screens, non-customer prompts.
CI and evals green, plus a senior reviewer → staging soak, then prod
T2
Critical
Core, auth, tenancy, migrations, anything that sends messages or money, and customer-facing agent behaviour.
Two reviewers including the Principal Architect → staged 5% → 25% → 100%
Trust, Woven In.
Every Product Built On Twillx Gets The Same Safety And Quality Guarantees, With Nothing To Bolt On Later.
Row-level security on every tenant table, tenant context carried through every request, event, workflow and agent, and automated leak tests in CI.
Anything an agent does that sends, deletes, pays or writes externally waits for a human first.
Instructions hidden inside an email or document can never trigger a tool call.
Every human and agent action goes to an append-only ledger that tenant admins can search.
Inputs, context, tools, outputs, cost, latency and approver are captured for every agent run.
A drop in AI quality blocks a merge just like a failing unit test, and live runs are scored daily.
One Choice
Per Layer.
Open source and replaceable: TypeScript for the platform and UI, Python for AI. Every choice can be self-hosted, so costs come from hosting, not licences.
- Experience
- Next.js + ReactTailwind + shadcn/uiStorybookReact FlowJSON Schema forms
- Services
- TypeScript · NestJSPython · FastAPIOpenAPI 3.1AsyncAPIGenerated SDKs
- AI
- LiteLLM gatewayMCP toolsTwillx agent runtimepgvector + DoclingLangfuse + Promptfoo
- Orchestration
- TemporalNATS JetStreamWebhooks in/outSchedulesDead-letter + replay
- Identity & policy
- KeycloakOpenFGAOpenBao / KMSPostgres RLSAudit hash chain
- Data
- PostgreSQLpgvectorValkeyObject storageMigrations in CI
- Delivery & ops
- GitHub ActionsOpenTofuKubernetes + Argo CDOpenTelemetryGrafana LGTM
Distinct products.
Shared fabric.
Four levels of UX extensibility, cheapest first. Each product looks like itself from day one, and still runs on one kit.
Design tokens only: colour, type, density, logo. Zero code.Dhoom, October and XODY look distinct on day one
Theme
Screens built from the UI kit inside the shared app shell.Navigation, sign-in, tenant switcher, command bar
Compose
A product-owned component package for its signature UX.Dhoom creative studio · October portal builder · XODY record pages
Extend
Twillx widgets inside other systems and surfaces.SIMS in Salesforce, Dynamics, Slack, Teams and voice
Embed
XODY on Twillx
AI code instead of low-code.
On Twillx, the customisation is generated code, so it can be tested, diffed, reviewed and rolled back.
- Describe — The admin types what they need. “Add a renewal-risk score to Accounts and alert the owner below 40.”
- Generate — A Twillx agent writes typed TypeScript and tests against the XODY SDK.
- Preview — The code runs in the tenant's sandbox, in a preview environment.
- Approve — The admin reviews the diff and test results. Critical changes need a second approver.
- Version — Each change is deployed per tenant with one-click rollback and an audit record.
| Low-code configuration | XODY AI-code on Twillx | |
|---|---|---|
| Artifact | Proprietary config, hard to inspect | Readable TypeScript with tests |
| Review | Clicking through screens | Diff, tests and evals in a PR-style review |
| Portability | Locked to the vendor's engine | Standard code against a published SDK |
| Ceiling | Whatever the builder exposes | Anything the SDK and sandbox allow |
| Rollback | Manual, by memory | One click, versioned and audited |
The road
to Twillx 1.0.
Five phases and four gates, from November 2026 to April 2027. A failed gate shrinks the next phase rather than moving the date.
Frame & harvest
Phase 0 · Nov
Lift what working products have already proved into a clean foundation.
Weave the core
Phase 1 · Nov–Dec
Tenancy, identity, gateway, workflows and agent runtime.
G1 · Fabric MVP
Lighthouse
Phase 2 · Jan–Feb
XODY SIMS live on Twillx with real traffic.
G2 · Lighthouse live
Second product
Phase 3 · Feb–Mar
October.ai or Dhoom.ai proves the reuse.
G3 · Reuse proven
Factory mode
Phase 4 · Mar–Apr
Every product team builds on golden paths.
G4 · Twillx 1.0Weave Your Next
Product With Us.
Three ways in, whether you want to shape Twillx, build on it or help us engineer it.
Become a design partner
Pilot XODY SIMS or another Twillx product in shadow mode, and shape the roadmap with our core team.
- Go from signed pilot to live traffic in about a week
- Agents draft in shadow mode before they send anything
- Fortnightly demo days with the team
Engineer with Virtuos
Your next platform, product or modernisation, built on the Twillx foundation by Virtuos engineering.
- Golden paths from day one
- Enterprise security built in
- AI-drafted, human-signed delivery
Join the Twillx team
Help build the foundation for AI-first engineering, alongside agents and engineers who care about craft.
- Platform, Fabric and experience roles
- Claude Code and Codex in daily use
- Open source at the core
One Foundation. Infinite Possibilities.
Build once. Compose endlessly. Engineer forwardly.