Regit

The Operating System for Investment Products.

One Golden Record per product. Oversight, filings, lookthrough, distribution: everything reads from the same source. When something changes, you update a recipe. The pipeline stays.

Documents and Distribution are live. Portfolio is in progress. Lifecycle and Onboarding are planned.

The platform

One Golden Record. Two modules live.

Oversight by design

Your regulator asks where a number came from. One query. Full chain.

Three stages: intake, computation, Golden Record. Each audited, each derivation traceable. From the delivered document back to the raw data row, the chain is intact.

Intake

Your data arrives

NAV feeds, cost spreadsheets, ESG data, custodian files. Every file is content-addressed and immutable from the moment of receipt. Nothing is overwritten. Nothing is discarded.

Computation

Derived, not hand-seeded

Volatility, VEV, MRM, CRM, SRI, performance scenarios. Satellite computations run deterministically from the source data. Every transformation logged with full provenance.

Golden Record

One canonical record per product

Versioned through time. Every field carries its derivation chain: source, computation, tool version, timestamp. Filings read from one place.

Lookthrough

Position-level transparency for Solvency II reporting.

Fund-of-funds holdings resolve down to the underlying position. TPT V7.0 lookthrough and QRTs S.06.02, S.06.03, S.08.01, and S.11.01 report on the actual portfolio, not the wrapper. Insurance supervisors see what they need to see.

Full lineage

One reference from data row to delivered filing.

Every published document carries an evidence trail: which data snapshot was fetched, which recipe version rendered it, which template it ran against, and where it was delivered. Open any filing, months later. The chain is still intact.

Coverage

26 live documents. 6 regimes.

The product-disclosure filings a Luxembourg ManCo, asset manager, or insurer owes across these six regimes.

PRIIPs

The complete PRIIPs KID under EU 1286/2014 and CDR 2017/653, across all four categories: the SRI (market and credit risk), performance scenarios and costs.
PRIIPs KIDLIVE

FinDatEx

EPT, EMT, EET, and CEPT. Current FinDatEx versions, for the standard distributor disclosure feed.
EPT V2.1LIVE
EMT V4.3LIVE
EET V1.1.3LIVE
CEPT V2.0LIVE

SFDR

Article 8 and 9 disclosures under EU 2019/2088, the 14 mandatory PAI indicators, and EU Taxonomy turnover, capex and opex KPIs.
SFDR Art. 8LIVE
SFDR Art. 9LIVE
PAI statementLIVE
EU Taxonomy KPIsLIVE

Solvency II

Full standard-formula SCR, technical provisions, own funds, MCR and group solvency, with the 24 EIOPA QRTs and TPT V7.0 asset look-through, filed as XBRL to the NCA.
QRT S.25.01LIVE
QRT S.23.01LIVE
QRT S.28LIVE
QRT S.29LIVE
QRT S.02LIVE
QRT S.05LIVE
QRT S.12LIVE
QRT S.17LIVE
QRT S.19LIVE
QRT S.21LIVE
TPT V7.0LIVE
QRT S.06.02LIVE
QRT S.06.03LIVE
QRT S.08.01LIVE
QRT S.11.01LIVE

UK FCA

UK equivalent of the PRIIPs KID, replacing it for UK-distributed products under FCA COBS 14.2A.
UK CCILIVE

Commercial

Distributor-facing and board-facing documents.
FactsheetLIVE
Board PackPLANNED
Distribution

Every dispatch logged.

Configurable rules define who gets what, when, and through which channel. Regeneration on data change: automated, human-validated, or policy-driven. Delivery confirmation recorded on every send.

Website

Client-facing fund pages generated from the Golden Record. NAV, performance, documents, and regulatory disclosures. Auto-updated on data change.

Email

Regulatory inboxes, compliance officers, distributors. PDF attachments on schedule or on trigger.

SFTP

Direct feed to distributor platforms and data vendors. EPT, EMT, EET, CEPT as CSV on the cadence each counterpart requires.

API

Automated notifications when a document is ready. Delivery status and filing confirmation sent to your internal operations systems.

S3

Bulk file delivery to cloud storage. Per-fund, per-ISIN structure. Client-isolated with controlled access for downstream systems.

NCA filing

XBRL delivery to the national competent authority: CSSF eDesk for funds, CAA e-file.lu for the EIOPA QRTs. Submission logged on upload.

Pipeline

One recipe per document type.

Recipes

Configuration, not release cycles.

A recipe defines what a filing contains, how it looks, and where it ships. Your operations team edits it, a second approver signs off, and the next filing run uses the new version. Four-eyes approval on every change. Ten-year retention on deprecated recipe versions.

Example recipes

PRIIPs KID (Fund)

priips-fund / v1.4

Four-eyes: 2 of 2. 10-year retention.

SFDR Art. 8

sfdr-art8 / v2.1

Four-eyes: 2 of 2. 10-year retention.

QRT S.25.01

sii-scr / v1.0

Four-eyes: 2 of 2. 10-year retention.

Use cases

Four desks. One answer.

CFO, quarterly close

Every filing, on the cadence the regime requires, without a cost centre that scales with regulation.

A ManCo spending on separate PRIIPs, FinDatEx, Solvency II, and SFDR vendors pays repeatedly for the same fund data and reconciles the same holdings snapshot across parallel pipelines.

26 document types. One platform. One evidence trail.
COO, monthly cycle

One operating picture. Ingest, derive, file, deliver, audit.

Distributors do not wait. When a KID bounces, your team locates the error, assembles the corrected inputs, and emails the revised file under time pressure. The audit trail is whatever the last analyst remembered to save.

KID on annual review and material change. EMT on change. QRTs quarterly.
Head of Operations, day to day

A recipe change is a filing change. No release train.

A disclosure footnote, a new risk band, a distributor’s EMT dialect: today these turn into change requests that sit in a dev queue for sprints.

Four-eyes recipe approval. Ops ships. No developer queue.
Chief Compliance Officer, continuous

Every filing generated on Regit walks back to the data, the recipe, and the approver.

Open a KID filed a year ago. The chain is still intact: data snapshot, recipe version, rendering run, delivery record.

Evidence trail from data to delivery. Ten-year retention on every artifact.
Nicolas Koenig, Founder of Regit

I've seen what breaks at scale. I built the infrastructure to fix it.

I spent years in technology, services, and infrastructure across Switzerland, Germany, France, and Luxembourg. When I looked at how the investment product world operated, I saw a problem I recognized: too many providers, no shared record, no common baseline for every regime. Funds, IBIPs, structured products: each regime handled by a different vendor, each with its own pipeline, its own snapshot timing, its own audit trail. Two disclosed documents for the same product can contain different figures. That is a structural problem, not an operational one.

The operating model I kept seeing was the same everywhere. Talented people, hired to do analysis, spending their time copying data between spreadsheets. Extended hours before filing deadlines. Blamed for failures that were built into the process, not caused by them. More products meant more of the same work, not smarter work. In my experience, the value produced per filing only went down.

My background is tech. I had seen this category of problem solved already: data pipelines, event-driven systems, modern data architecture. The patterns existed. Fund services had never received them. So I architected Regit from first principles: one shared record across every regime, designed so that compliance obligations can be met systematically, built for sovereign deployment, with an agentic orchestration layer whose tools are deterministic: the automation runs the same computation every time, and lets talented people focus on oversight and analysis, not data entry.

Designed for Luxembourg fund operations, for the people who run the process.

Nicolas Koenig, Founder

Luxembourg

Built in Luxembourg. Based at 26 Boulevard Royal.

Deployable on sovereign, private, or public cloud. DORA ICT risk information, data residency posture, and the sub-processor list available on request.
Controls aligned to NIST 800-53v5 and NIST CSF.
SOC 2, ISO/IEC 27001, and ISAE 3402 on roadmap.
Contact

Tell us what you run.

Products, regimes, document types, cadences, the team that owns the filing today. A short note is enough to start. We aim to reply within one business day, Luxembourg time.