Era by Eon - super realistic simulated companies

Timestamps land when people are at work

Every record's time is drawn against its owner's working week, in their own timezone.

78% inside business hours, 6% at a weekend. Holidays are per country.

A person has a level, a history and a residue

One human, derived once: a seat, a rung, a string of moves, a year with leave in it, and what is left behind when they go.

Numbers come from published shapes, not uniform noise

Each target carries where it came from, and the table the generator draws from is the table it is scored against.

One outage, five customers, five different sentences

Unrelated accounts file about the same failure, each from their own timezone and in their own words.

19% of the queue belongs to a shared incident, one day in 30, and they land midweek because deploys do.

The mess is on purpose, and declared

A tenant can be dosed with the housekeeping a real company has: a pasted placeholder, a spreadsheet's casing, the test account from 2023.

Opt-in and declared, so it benchmarks deduplication, DLP and access review instead of being noise.

Many kinds of data, at the volume a real estate carries

The same company is projected into tabular systems, file stores, call transcripts, chat and rendered documents - and one tenant at the top size tier carries tens of thousands of records in each of them.

• 11systems carry a projection of the same graph: six tabular overlays and five file stores, all agreeing on who works there and what happened
• 79,000entries read back off one 20,000-document estate through Drive's, Box's, Dropbox's and AWS's own SDKs - every document in all of them
• 12,050of the tenant's files are rendered documents and 750 are call transcripts, not rows with a filename

Volumes are one hyperscale segment's published answer key, the same file its graders are scored against; the four-store figures are the files-and-lake audit that drove each vendor's SDK across one estate and joined the results back to the graph.

Nine ways to spot fake data. Ours trips none of them.

Every number stands beside the same company generated the naive way.

Every company, every check and everything the detector found is published in full on Data fidelity.

Connect to the live stack, not a snapshot

Every system in the company is a running instance. An agent connects over MCP, a client over the vendor's own API, and both read and write the same tenant.

Every connector serves its vendor's REST API and an MCP endpoint off one port, against one tenant's state, so a write over MCP is there when the REST client reads it back.