Fignix product 05 · Axon

The running product is
the only source of truth.

Axon is an agent that continuously uses your product, keeps a versioned and verified model of it, and renders that model for people as videos and docs, and for AI agents as specs.

Open Axon ↗How it works ↓

Free while in beta, by invitation. Sign in with your Fignix account; a product URL is all Axon needs to start.

Axon's overview of Talo: what Axon found in four areas, six features and eleven screens, the reality audit counts, and the latest video. — Actual Axon interface, looking at Talo, another Fignix product. Select the image to view full size.

BUILT FORFounders whose product outruns its docsProduct and DevRel teams shipping dailySales teams who demo a moving target

What Axon does

Look. Verify.
Render for people and agents.

Software now ships faster than anyone can document it, film it, or demo it. Axon does not ask what the product does. It finds out, keeps the evidence, and makes everything downstream from that.

It uses the product, not the docs

Give Axon a URL. It opens your product in a browser on its own server, moves around like a user, records every flow it carries out, and keeps the recordings as evidence.

A product map that stays current

Screens, controls, flows and features, grouped into areas. Every look is a numbered snapshot, so you can see what the product was on any date.

A reality audit of your claims

Axon reads your marketing site and docs, lists what they promise, and checks each claim against what it saw. Verified, unverified, contradicted, or undocumented.

Videos from real recordings

Faceless vertical videos narrated from the product model: a full tour, or only what changed since last time. Every scene cites the screen or flow it shows.

Docs and a changelog, kept current

Feature pages and how-tos written from the snapshot, and a public what's-new page Axon hosts for you. Each release updates both, or waits for your approval.

Demos written for one prospect

Paste a prospect's website. Axon works out what they do, proposes which features to show and why, and renders a video, a slide deck and a one-pager with a share link.

Files for the agents that buy software

llms.txt, playbooks and a spec, plus an MCP server, so AI agents learn what your product does from what was actually seen rather than from a guess.

Your instructions, remembered

Standing instructions, a never-press list, a checkpoint before rendering, and rules learned from every edit you make to a script or a proposal.

The release loop

Every release
makes Axon look again.

Install the Axon GitHub App on a repository and each published release starts a look, with the release notes as the why and the changed files steering where Axon spends its time. No repository? A webhook, a browser-extension walkthrough, or one button does the same.

releaseA release is published on GitHub, a webhook fires, or you ask
lookAxon opens the product and spends its budget where the release changed things
compareThe new snapshot is compared with the last one; only what a user would notice counts
renderWhat's-new video, updated docs and a changelog entry, from the recordings
publishStraight to the public page, or held for your review first

Axon's product map for Talo: the Company discovery area with its screens and a recorded flow, Browse the Data & AI category, marked carried out. — Each flow Axon carries out is kept as a recording, so the map, the videos and the docs all point at the same evidence.

Reality audit

What you claim,
checked against what is there.

Claims are read from your public pages and each one gets a verdict with evidence: the screen or flow that shows it. Undocumented features surface too, so the public story and the product stop drifting apart.

Axon's reality audit for Talo: a list of claims from the home page, each marked verified with the screen Axon saw. — Actual Axon interface · Talo example · Select to view full size.

Releases

A changelog written
from the product itself.

Each release compares two snapshots and lists what a user would notice, with a what's-new video recorded from the new flows. Axon hosts the public page; you decide whether entries appear on their own or after you have read them.

Axon's Releases tab for Talo: a public what's-new page link and a snapshot comparison describing a fit check feature that was added, with its video. — Actual Axon interface · Talo example · Select to view full size.

Sales demos

One demo per prospect,
in their words.

Axon reads the prospect's site, proposes an angle and the features to show, and you edit before it renders. The share link carries the video, a slide deck and a one-pager, and tells you when it was viewed.

A demo page Axon made for Razorpay: a headline about competitor hiring, the demo video, and links to the slide deck and one-pager. — Actual Axon interface · Talo example · Select to view full size.

How Axon works with you

Nothing is published
without you.

Axon only claims what it saw. A video scene, a docs page or a changelog entry always cites the screen or flow it came from, and the recording is kept.

You can give standing instructions, name controls Axon must never press, review every script before it is narrated, and hold releases until you have read them. Every edit you make becomes a rule for the next run.

Credentials are optional. Start from a public URL or a walkthrough in your own browser with the Axon extension, and add a sign-in later if you want Axon to go further on its own.

Start with a URL

Let Axon use your product.

Add the address of your product, and within minutes you have a product map, an audit of your claims and a first video, all made from what Axon actually saw.

Open Axon ↗Free during beta · Invitation only · Shared Fignix sign-in