Free
$0free forever
Every sign-up starts here.
- 1 product, 1 data source
- 50 insight credits a month
- Full trace visible
- Buy credit bundles any time
- Data sources are removed after 30 days without use
A stadium operator runs its match days on its own platform. STEWARD is embedded inside it. When a decision cannot wait, STEWARD reads the operations manual and the live ticketing the moment the operations lead asks, and answers with its sources.
STEWARD reads ticketing and ingress counts live, by gate, the moment the operations lead asks. Not last night's snapshot.
Your operations manual answers from the knowledge base, cited by section, and resolved against the live counts.
STEWARD builds arrival models from live counts in a sealed sandbox with no network, and returns the chart with its sources.
Live reads inherit the asker's permissions. An arrivals question needs counts by gate, not ticket holders' names.
A rail operator's recovery is not in your material, so STEWARD says so.
STEWARD reads. The safety officer opens the lanes. STEWARD never opens a lane.
$0free forever
Every sign-up starts here.
$490per year, or $49 a month2 months free
One product, one team.
Everything in Free, plus
Most chosen
$2,990per year, or $299 a month2 months free
A product company, or an agency's client book.
Everything in Starter, plus
Custom
Sold by contract.
A delivered answer costs one to five credits, by depth. An answer that never arrived costs nothing. No seats. No overage.
STEWARD answers match-day questions from the operations manual and live ticketing and ingress counts, under each operator's own login, with sources. It builds arrival charts from live counts in a sealed sandbox with no network.
STEWARD reads the REST API you configure. It reads no rail or transport feed, so the operations lead gives the delay in the question.
STEWARD's live reads inherit the asker's permissions. An arrivals question needs counts by gate, not names.
STEWARD records source, time, input, output. Logged and exportable. STEWARD does not record who asked.
STEWARD's live reads need a host application with signed-in users, because STEWARD borrows their token. A public site without login gets knowledge-base answers only.
AWS services alone process STEWARD's institutional content. AWS Bedrock is the sole model provider.