The sharable.link alternative with company sign-in
Everything sharable.link sends,
without the shared password.
sharable.link is the closest product to our own agent route: a free remote MCP server that publishes from Claude, Cursor, Cline or Windsurf, keeping the URL when you update. The difference is the gate. Theirs is a password on the page. Ours is company identity, so every view has a person against it.
Route 01 – from your agent
Same one-sentence publish.
A prompt, a command or an MCP call from Cursor, Codex, Claude Code or any other agent.
Copies the full prompt, including what your agent should do once the URL comes back.
Route 02 – from a file
Or publish a file yourself.
One HTML or Markdown file, and no sign-in before you see it work.
No file to hand?
- html + markdown
- up to 50 MB
- no signup
Either route returns a URL and a claim link. Claim it and the gate becomes identity, not a password.
Indigo Engineering
What sharable.link does
It runs as a remote MCP server at one URL with nothing to install, exposing tools to share a page, update it, unshare it and list what you have published. It works from Claude, Cursor, Cline and Windsurf. Publishing through the connector needs a free Google or Microsoft account, though dragging a file onto its upload page does not, and viewers never need one. It is free, with unlimited links and storage under a fair-use policy, and pages can be password protected. Updating keeps the same URL.
That is a well-built product, and on the publishing mechanics the two are close to even. Where they diverge is what happens after the link leaves your hands.
Facts about sharable.link are from sharable.link, checked 10 August 2026.
display.dev vs. sharable.link
| display.dev | sharable.link | |
|---|---|---|
| Remote MCP server | ✅ | ✅ |
| Publish from Cursor, Claude, Windsurf, Cline | ✅ | ✅ |
| Update in place at the same URL | ✅ | ✅ |
| Password protection | ❌ (identity instead) | ✅ |
| Publish with no account | ✅ | Upload page yes; MCP needs a free account |
| Restrict to named email addresses | ✅ | ❌ |
| Google + Microsoft SSO for viewers | ✅ (Pro) | ❌ |
| A name against each view | ✅ | ❌ |
| Inline comments an agent can read back | ✅ | ❌ |
| Publish from a terminal or CI | ✅ (dsp publish) | ❌ |
| Organization ownership and audit log | ✅ | Enterprise |
| Price | Free tier, then €15 / €49 | Free |
When sharable.link is the right tool
- It is free, and it is good
- Unlimited links at no cost is a real advantage, and worth saying plainly. If budget is the binding constraint, use it.
- The reader is outside your company
- A friend, a client with no shared identity provider, a public audience. There is nothing for SSO to attach to, and a password is a reasonable gate.
- You only need the publish loop
- Share, update, unshare, list. If nobody is going to comment on the page and nobody needs a viewer list, that is the whole job and it does it.
A password cannot tell you who read it
The gap is not the publishing. It is what a password can and cannot express once the page holds something that belongs to a company.
- ✗One secret, everyone who has itA password is held by whoever was told it, including whoever they told.
- ✗Revoking is all or nothingChanging it removes access from every reader at once, including the ones you wanted.
- ✗No name against a viewNothing to show later about who actually opened the analysis.
- ✗No company boundary"Only
@acme.comaddresses" is not something a password field can express.
Who can open it
An open URL, served with noindex, when the content is genuinely public.
Named email addresses, each with a one-time password by email. Access is per person, and so is removal.
On Pro, Google Workspace or Microsoft Entra ID decides. Your identity provider is the source of truth, so offboarding closes the page without anyone rotating a secret.
And the loop keeps going. Colleagues leave inline comments, your agent reads them back over MCP, publishes a new version at the same URL, and resolves the thread.
Pricing
Try it. No credit card.
- Included: 10 gated artifacts
- Included: Unlimited public artifacts*
- Included: 50MB storage
- Not included: Version history
- Not included: Google + Microsoft SSO
- Not included: Private artifacts
- Not included: Audit logs
display.dev branded
Individuals. Unlimited gated sharing.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 1GB storage
- Included: 10 versions
- Not included: Google + Microsoft SSO
- Not included: Private artifacts
- Not included: Audit logs
For teams that need company auth.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 25GB storage
- Included: 50 versions
- Included: Google + Microsoft SSO
- Included: Private artifacts
- Included: 90 days audit logs
For compliance-driven organizations.
From €499/mo
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: Custom storage
- Included: Unlimited versions
- Included: Google + Microsoft SSO
- Included: Private artifacts
- Included: 365 days audit logs
Try display.dev free
- Company sign-in instead of a password box – with a name against every view
- Inline comments your agent reads back, at the same URL
- First artifact in 15 seconds · No credit card
Common questions.
Is sharable.link worse than display.dev?
No, and on the parts that overlap it is very close. Both run a remote MCP server, both publish from several agents, both keep the URL stable across updates, and theirs is free. Pick display.dev when the page needs identity-based access – named people or your whole company – rather than a password, or when you want inline comments and an audit trail.
Can I publish without an account?
Yes: you get a URL and a one-time claim link with no account at all, and viewers of a public page never need one either. sharable.link is the same for its drag-and-drop upload page; publishing through its MCP connector asks for a free Google or Microsoft account first.
Can I still password-protect a page here?
No, deliberately. Access is by identity – a one-time password sent to a named address, or company SSO. Both tell you who opened the page; a shared password cannot.
Which agents can publish to display.dev?
Cursor, Codex, Claude Code or any other agent that can run a command or make an HTTP request, plus the CLI and CI pipelines through dsp publish.
What happens to comments my colleagues leave?
They are inline on the artifact, and your agent can read them back over MCP, publish a new version at the same URL, and resolve the thread.
Publish your first artifact in 15 seconds.
Free tier. No credit card. One-time password auth on free, Google + Microsoft SSO on Pro (€49/month flat).