Planning workspace
Company priorities
A shared plan for the next chapter.
Org-managed AI artifacts
Connect your agents and publish documents and sites to a company-owned link—with access controls built in.
Planning workspace
A shared plan for the next chapter.
Customer synthesis
Patterns from 42 customer conversations.
Component library
Live performance
Revenue, retention, and momentum in one place.
Whatever AI model your team uses, the result is an org-owned link with granular access built in.
acme.every.link/2026-marketing-insightsHow it works
MCP is the direct path for web AI. Coding agents use the official skill and CLI. Drag and drop remains available for a manual one-off.
Create your-org.every.link—a company-owned home for everything your team publishes.
Add the remote MCP server to a web AI tool, or install the official skill and CLI in a coding agent.
Ask your agent to publish. Each member connects as themselves, and every deploy inherits the site URL and access rules.
Access
Set it per site, change it later, and the URL never moves.
Anyone with the link. Turn on indexing when you want it found.
One shared password, no account needed.
Named people, or anyone on your email domain.
Backend, optional
Create a collection and its schema in the dashboard. Your site gets REST endpoints on its own path.
Collection schema
{
"type": "object",
"required": ["name"],
"properties": {
"name": { "type": "string" },
"note": { "type": "string" }
}
}Your site
await fetch('/spring-campaign/_data/entries') await fetch('/spring-campaign/_data/entries', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ data: { name, note } }) }) // Requests stay on the site origin.
Agent-first publishing
Agents upload the files they create and return the live URL. Choose the connection that fits your tool; use the dashboard when you want to handle a one-off yourself.
Add the remote MCP server, sign in as yourself, and let the agent publish Markdown, HTML, or files directly.
Install the official skill. It uses the CLI to inspect local files, avoid unsafe inputs, and publish the right folder.
Drag in HTML, Markdown, a ZIP, multiple files, or a folder from the dashboard when no agent is involved.
14 files · published by Maya via Claude · deploy #42
FAQ
Anything static. A web AI tool can upload it through MCP; a coding agent can publish it with the skill and CLI; or you can manually drag in HTML, Markdown, a ZIP, files, or a folder. Markdown becomes a styled page.
every.link gives your company more control after that work leaves the chat. Each site gets a stable company URL, its own access rules, a record of who published it, past versions, and one-click rollback.
The link stays with your company when people, models, accounts, or chats change. Teams can publish from an AI chat, a coding agent, the command line, or by dragging in files. Sites can also add uploads, data, and connections to other tools.
No. Each member authorizes their own AI connections, so publishes can be traced to both the person and the connected app. Admins can review and revoke access without seeing anyone’s secret.
Only on sign-in-required sites. Public and password sites need no visitor account, and viewers are never billed.
No. A site keeps its URL while each publish creates an immutable deploy you can inspect or roll back to.
A JSON collection API for prototypes and internal tools. It is not positioned as a general-purpose production datastore.
Join the private beta and claim your account subdomain.