0:00 · A shared home for reports
User: Can my team explore the data themselves?
Agent: Build reports in a repository, then use the optional portal as your team's shared home.
Trellum · Product tour
A tour of the self-hosted portal
See how a team can publish reports, follow shared definitions and manage its reporting workspace. This captioned feature tour uses real portal screens and illustrative dialogue; it is not a recording of an agent session.
Transcript and capabilities
The dialogue below is illustrative. Screens show the seeded Nova Play and Product Insights portal with synthetic local SQLite and CSV data. No remote Git repository, Buddy provider or email service is configured in this demo.
0:10 · Connect your sources
User: Use our database and acquisition budget.
Agent: Declare source names in the project. An admin supplies credentials. This demo uses synthetic SQLite and CSV data.
0:24 · Build with your coding agent
User: Create a revenue and retention report.
Agent: Use Codex, Claude Code, or your preferred agent to edit Python, SQL and YAML, build locally, and validate the output.
0:40 · Define metrics once
User: Keep revenue consistent across reports.
Agent: Define it in metrics.yaml. Reports claim metric IDs; the catalog shows their definitions, versions and usage.
0:52 · Review and publish with Git
User: Show me the changes before publishing.
Agent: Review the diff and commit history, then publish the reviewed revision. This screen connects your repository; the demo has no remote configured.
1:06 · Put events beside the numbers
User: Mark releases and campaigns.
Agent: Add events.yaml declarations in Git. The portal calendar and report charts show their context.
1:18 · Follow the whole experiment portfolio
User: Which tests are running, and what changed?
Agent: The overview reads declared tests and their built results, including confidence intervals and lifecycle status.
1:30 · Schedule and inspect builds
User: Keep reports fresh and show failures.
Agent: Operations shows schedules, build status, validation and logs. These demo builds completed successfully.
1:42 · Control access and sharing
User: Can we share a report safely?
Agent: Use organization and studio roles, plus configurable share links, passwords and expiry. Sharing is disabled in this demo.
1:54 · See which reports get used
User: What does the team actually read?
Agent: Report Analytics tracks views and unique viewers so you can review report usage.
2:04 · Query at view time when needed
User: Can some reports show current detail?
Agent: Authors can declare live queries. They need a backend; the organization controls query limits.
2:14 · Describe what should trigger an alert
User: Watch for a drop in retention.
Agent: Write a report-specific rule in plain language. This unsaved example needs an AI provider and delivery setup before it can run.
2:28 · Ask questions inside the portal
User: Can readers ask a follow-up question?
Agent: Optional Buddy uses an administrator-configured model provider. It is separate from your coding agent and is not enabled here.
2:42 · Reports that people can explore
User: What else can a report show?
Agent: Store Health is a separate retail example: comparison KPIs, filters, chart annotations, revenue and margin in Trellum Dark.
2:54 · Try Trellum
User: Where do I start?
Agent: pip install trellum. Browse report demos at trellum.dev/demo, or run the portal locally.
Choose how to explore Trellum
The public gallery is a set of interactive reports only. The portal is a separate backend that you run and administer yourself.