Engineering
We built a fake social network so you could try a real product
May 28, 2026 · 7 min read
The worst part of evaluating a social media tool is that you can't, really. Either you hand a stranger OAuth access to your actual audience on day one, or you watch a two-minute video of someone else's dashboard and try to extrapolate.
We refused both. When you sign up for Rysonance, you connect a simulated account — and the entire product runs against it. Not a subset. The same inbox, the same voice training, the same auto-pilot, the same analytics.
What the simulator actually does
- —Generates a posting history — 120 posts in a consistent voice — so personality training has something real to learn from
- —Maintains a cast of 30 recurring personas, from lurkers to verified accounts, who mention you at realistic hours
- —Keeps the feed alive over real time: come back tomorrow and new mentions arrived overnight
- —Grows engagement on posts the way it grows in the wild — fast at first, long tail after
- —Backfills 90 days of analytics so the charts mean something on your first visit
The interesting constraint is determinism. Every mention is generated from a seed derived from your account and a time bucket, which means syncing twice never duplicates anything, and the feed behaves identically whether you check it once an hour or once a week.
Why bother
Because the simulator forced us to build the product honestly. Every service — reply generation, relationship scoring, scheduling, analytics — talks to a platform interface, and the simulator is just one implementation of it. Twitter and LinkedIn are others. Nothing above that interface knows the difference.
If your demo needs a different codepath than your product, one of them is lying.
So the demo isn't a marketing asset that drifts out of date. It's the product, pointed at a world we can afford to let you break.