A company that keeps living after you generate it.
Static fixtures test one frozen moment. Real software handles a business that changes — month-end, renewals, churn, a fraud pattern that emerges over six weeks.
The simulation clock
Every company has a clock you control. Advance it and the business generates the events a real one would — new invoices, payments, hires, deals closing, churn — all still reconciling.
fictix advance 1d # one business day
fictix advance 30d # to month-end
fictix advance --to renewal # to the next contract renewal
fictix logs --follow # stream the event logPause it for a deterministic snapshot, or let it trickle so data arrives continuously like a live integration would see.
The seven dials
Company behaviour is shaped by seven controls:
| Dial | Governs |
|---|---|
| Growth | Revenue and customer acquisition trajectory |
| Churn | Customer loss rate and contraction |
| Chaos | Operational messiness — late entries, corrections |
| Fraud | Intensity of fraud-shaped patterns |
| Seasonality | Cyclical revenue/expense swings |
| Maturity | Process discipline of the finance org |
| Trickle rate | How fast new events arrive in real time |
Events you can subscribe to
As the clock advances, Fictix emits webhooks with signed payloads and retry semantics — so you can test event-driven flows (reconciliation triggers, alerting, sync) against a stream that behaves like production, not a one-shot fixture.
Why it matters for detection
The hardest anomalies aren't present at t=0; they emerge. A duplicate that surfaces three weeks in, a fraud ramp across a quarter — the living simulation plants needles in time, not just in place, so you test detection the way it actually has to work.
Questions
Can I control how fast data arrives?
Yes — the trickle-rate dial ranges from paused (deterministic snapshot) to a fast continuous stream, and you can jump the clock to a specific state like month-end or renewal.
Does the data stay consistent as time advances?
Yes. Generated events keep the whole company reconciling across systems as the clock moves.
Can I test webhook-driven flows?
Yes. Advancing the clock emits signed, retrying webhooks so event-driven integrations get a production-shaped stream.