Home / Company

Systems we build

Rillor builds and operates AI and data systems over large bodies of text and market data. Each runs in production and shapes how we build for clients.

Data

Market data warehouse

A research warehouse of U.S. equity and futures trade and quote history from 2018, alongside order-book data from on-chain perpetual futures venues, aligned on one clock.

Used to calibrate simulated markets, test forecasting methods and check rule models against recorded transactions.

How the market data warehouse is built and usedTwo sources, U.S. equity and futures trades and quotes from 2018 and on-chain perpetual futures order books rebuilt from snapshots and book diffs with fills, liquidations and funding, feed one aligned warehouse with one clock and one symbol map. The warehouse is used to calibrate simulated markets, test forecasting methods and check rule models against recorded transactions.U.S. equities and futuresTrades and quotesfrom 2018On-chain perpetual futuresOrder books rebuilt fromsnapshots and book diffsFills, liquidations, fundingAligned warehouseOne clockOne symbol mapSimulated marketsCalibrationForecasting methodsOut-of-sample testsRule modelsChecked againstrecorded transactions
Sources, alignment and usesCoverage window stated in each dataset record
How it works
Perpetual futures order books are rebuilt from snapshots and book diffs, with fills, liquidations and funding. Equity and futures trades and quotes share the same clock and symbol map, so events from different sources line up.
For clients
We take high-volume, time-sensitive data from capture to research-ready tables. Custom datasets and client research are built the same way.

Agentic AI

Grellum

Agentic legal research, independently branded and run at grellum.com. It answers research questions over a legal corpus, and every citation must match retrieved evidence.

Grellum deep modeA question goes to a planner, which assigns parts of it to four to six specialist agents. The agents retrieve evidence from the decision corpus. An audit step checks every citation against the corpus before the answer is returned with citations.QuestionPlannerSpecialist agentsFour to sixAudit stepAnswerwith citationsRetrieve evidenceMatch everycitationDecision corpusLegal decisions and authorities
Deep mode, from question to cited answerEvery citation traced to its source
How it works
In deep mode, a planner assigns parts of each question to four to six specialist agents, and an audit step reviews their work. Every citation must match retrieved evidence.
For clients
Multi-agent research over a large corpus can be held to its sources. We apply the same design to document, regulation and policy work for clients.

Infrastructure

The Rillor platform

The infrastructure every Rillor product runs on: Kubernetes, distributed storage, GitOps deployment and network-policy isolation between tenants.

The Rillor platformGitOps deploys changes to a Kubernetes layer that enforces access control, admission rules and network policies. Three tenants run above it, each inside its own policy boundary. Distributed storage with block volumes and shared file systems sits underneath.GitOpsChanges shipfrom GitTenant AOwn namespaceTenant BOwn namespaceTenant COwn namespaceKubernetesAccess control, admission rules, network policiesDistributed storageBlock volumes and shared file systems
Dashed lines mark each tenant's policy boundary109 isolation tests passed, 7 Oct 2026
How it works
Changes ship from Git. Each tenant runs in its own namespace, bounded by access control, admission rules and network policies.
Isolation tests
109 access, admission and network tests passed for tenant isolation, run on 7 Oct 2026.
For clients
We build and operate private AI environments ourselves. Client deployments use the same patterns, on infrastructure the client controls.

AI tooling

MegaMCPs

Governed access to business tools for AI assistants, through an isolated MCP server for each customer.

One isolated MCP server per customerCustomer A's AI assistant connects to an MCP server isolated for customer A, which connects to customer A's business tools. Customer B has its own assistant, server and tools. No tool runtime is shared between customers.AI assistantCustomer AMCP serverIsolated for customer ABusiness toolsCustomer A's accountsNo shared tool runtimeAI assistantCustomer BMCP serverIsolated for customer BBusiness toolsCustomer B's accounts
Each customer's tools run in that customer's servermegamcps.com
How it works
Each customer's assistant connects to its own MCP server. Tool connections run inside that server, and no tool runtime is shared between customers.
For clients
AI assistants can use business tools with access governed per customer. Private AI cloud deployments include the same governed tool access.

Document AI

Public-records intelligence platform

A platform that archives public procurement records and regulations, extracts their document text and tracks how they change.

How the public-records platform processes documentsRecords and attached documents are archived as published. Text is extracted, with OCR for scanned files. Versions are compared and changes logged. The result is a record with text, fields and version history.ArchiveRecords and theirattached documentsExtract textIncluding OCRfor scanned filesTrack changesVersions comparedand changes loggedRecordText, fields andversion history
From published document to tracked recordSources: public procurement records and regulations
How it works
Records and their attached documents are archived as published. Text is extracted, with OCR for scanned pages, and each new version is compared with the last so changes are recorded.
For clients
Document AI at archive scale, from capture to extracted text to change history. The same approach fits any body of documents that changes over time.

Tell us what you want to build.

Build with us