Skip to main content
Live Apps let every room publish a real web app on top of its tables — a board, a tracker, a worklist, a directory, a dashboard. Start from a template or describe your own in plain English; either way the app binds directly to your room’s data, and Corvic hosts it at a URL you can share.
Live Apps live inside a Room — open the Live Apps surface from the room’s surface switcher, next to Chat, Playbooks, Memory, and Lens.

Everything a real web app needs, already attached

Built on your data

Pages read your room’s tables directly — no export, no copy to maintain.

Live, not a snapshot

Data is read when the page opens, and a scheduled workflow keeps the tables fresh.

Hosting is included

No server, no build, no deploy pipeline. Every app comes with a URL.

The data plumbing too

Connectors, pipelines, and tables are part of the platform, wired by the agent.

Pages, not a page

Multiple routes, its own navigation, and search and filters throughout.

Shared with a link

Your org opens it with their login, or publish a read-only public link.

How an app gets made

1

Pick a template or describe it

Browse Start from Template on the Live Apps surface and click Adopt this template, or click Build an app and tell Corvic what to build — anything that runs in a browser: a live dashboard, a website, an internal tool, even a game or a page that fetches a live API.
2

The agent builds and binds it

Each app gets its own builder agent and thread. The agent writes the pages and points them at the tables in your room, reusing an existing Workflow or provisioning one as it goes. Watch it come together in the app canvas, which has three tabs:
  • Preview — the running app. Use Select element to point at anything on the page and ask for a change.
  • Code — the app’s pages and spec.
  • Data — the app’s Connected data: the pipelines, sources, and tables it binds to, with run and schedule controls.
3

Share the link

Send it to the team — members open it with their Corvic login, or publish a read-only public link. Put the app’s workflow on a schedule and it stays current.
A template adopted before its data is bound shows a Preview badge and runs on sample data. Bind it to your tables from the Data tab to make it live.

Templates

The template gallery covers the common shapes of internal tooling — procurement, supply chain, OKRs, content calendars, team directories, personal finance, and dozens more — each running live on sample data so you can click through it before adopting. A blank canvas is there for anything that isn’t on the list. Adopted apps appear under My Apps.

What “live” means

Pages read the room’s tables at view time — opening the app always shows what the tables hold right now, with no baked-in copy of the data. Getting new data from your sources is the job of the app’s workflow: run it on demand from the Data tab, or put it on a schedule so the tables (and therefore the app) stay current on their own.

Workflows

The pipelines that keep an app’s tables current on a schedule.

Corvic Tables

The tables an app’s pages read at view time.

Data Sources

Connect the files, databases, and APIs behind an app.

Sharing

Share apps and artifacts with your org or via public links.

Virtual Memory

Query-ready knowledge an app or its agent can draw on.

Playbooks

Automate the recurring work that feeds an app.