What is important to me right now?
Vivport exists to answer that question honestly for anyone accountable for work getting done.
Everything a business runs on — email, documents, photos, calendar — arrives in one place and becomes structured evidence: decisions, actions, faults, questions, and risks extracted, anchored to the job, each carrying one immutable origin. Agents then do the work on top of it, under permission checks and approval boundaries, with the audit attached.
Get in TouchThe five kinds
Decisions, actions, faults, questions, and risks are what any organisation's communication is made of. They are not industry-specific.
Decision
Directs someone to act or spend.
Action
New work.
Fault
Rework caused by an earlier mistake.
Question
Needs answering only.
Risk
An exposure nobody has been told to own.
How It Works
Connect
Gmail and Microsoft 365 connect for mail and calendar import — per member, at most one account per provider.
Capture and extract with provenance
Anchors — jobs, projects, matters — sit at the apex of a governed content graph, with documents, events, and messages structured around them and photos, recordings, files, and URLs attached as evidence.
Imported messages are triaged automatically; obligations are extracted as Decisions, Actions, Questions, Risks, and Faults.
Extracted obligations are severity-scored and surfaced urgency-ordered — overdue, due soon, undated. Saved filters become tabs in the Explore workspace.
Work with Neo
Neo, the AI operator, creates anchors, documents, and events, sets up standing document maintainers, and navigates you around the product.
Neo writes research documents with live web research and per-section source citations.
Neo drafts and revises email replies — the member always presses Send.
Neo proposes calendar events through an editable composer — the member creates the event and decides the invites.
Automate under approval
Background Agents share Neo's tool language. Processes fire on triggers — a tag being applied, a file upload, a schedule, a matched inbound email, or a mail import — and a process that deliberately declines to act has that decision recorded too.
A standing maintainer keeps a target document up to date against a member-authored objective; every refresh is a reviewable revision.
Key Features
Every piece of content carries exactly one immutable origin — a Neo conversation, a process run, or a member's manual session — so 'where did this come from and why?' always has one auditable answer.
Documents revise through SUPERSEDES chains with stable codes — history is kept, never overwritten.
The Hub is a hard tenancy boundary — a business's content, permissions, and automations never leak across hubs.
MFA and passkeys (WebAuthn) on accounts, with per-hub permissions and groups.
All mutations go through a registry of governed tools with permission checks, scope checks, approval boundaries, and automatic provenance.
Agents, Processes, Skills, Tags, Tag Groups, and Filters are member-scoped, with deliberate promotion to hub scope — the UI is for inspection, approval, and audit.
Hub admins get Mission Control — process-run visibility and automation health.
Read-only external tools can be mounted for Neo via hub-configured MCP server connections.
Talk to us
Vivport starts with project-delivery businesses — teams whose work is organised around jobs, projects, and matters.