What your agency builds, on
your domain
A page built by your agency or by AI can live on your domain, with your access controls and your analytics.
Upload a compiled static site as a .zip and linkable.id hosts it at yourdomain.com/c/slug/. Every upload is a version, the code runs in a sandbox, and the page gets its own short link, QR code and stats.
Landing pages that live outside your control
An agency hands over a campaign landing page, or someone on the team generates one with an AI tool, and it ends up on separate hosting. It isn't on the institution's domain, neither marketing nor IT knows who can change it, it has no access rules, and its traffic doesn't show up with the rest of the campaign.
Hosting that follows your brand's rules
Your build, on your domain
Upload the output of React, Vue, VitePress, Docusaurus or a similar tool and the page lives at yourdomain.com/c/slug/. Single-page app mode keeps client-side routes working, and multi-page docs sites work as they are.
Public, private or visitor pass
Only members of your workspace can open a private page. For someone outside, issue a visitor pass with a password, an expiry date and a usage limit. Private pages and pages opened with a pass never show up in search results.
Versions and one-click rollback
Every upload is a new version that replaces the previous one with no downtime. If an upload fails validation, the live version keeps serving and you're told what to fix. Going back to an earlier version takes one click.
Security sandbox
Every page runs under a strict content security policy that blocks cookies, browser storage, eval and calls to undeclared services, so its code can't reach your private pages or other customers' data. A mode that serves each page from its own origin is rolling out, for public pages only.
Declared third parties
If the page uses outside services, you declare them: known providers like Google Analytics, Calendly, HubSpot or YouTube, or your own domains. From then on the page can only call that list, and changes apply without re-uploading the build.
Short link, QR code and analytics
Like any other linkable.id content, each custom page has its own short link and QR code. Visits break down by country, device, browser and source, with humans separated from bots, and show up in the workspace Snapshot.
What marketing teams use it for
The landing page your agency delivers
The agency hands over a .zip, your team uploads it as a private page, reviews it and publishes it on the institution's domain. No need to give the agency its own hosting.
Outside review with a visitor pass
Before launch, share the page with a vendor or an outside advisor through a visitor pass that expires and asks for a password, without creating an account for them.
Guides and documentation sites
An app guide or a customer manual built with VitePress or Docusaurus, published under your domain with its own link and stats.
Pages Claude builds
With the Claude connector, Claude builds the page, uploads it and can roll back to an earlier version. The page starts private, and publishing it takes a separate permission.
Frequently asked questions
It's a static site built by your team, your agency or an AI tool, uploaded as a .zip and hosted by linkable.id at yourdomain.com/c/slug/. It works with builds from React, Vue, VitePress, Docusaurus and similar tools, and it gets a short link, a QR code, access rules, versions and stats.
A branded page is assembled without code from widgets, your theme and Brand Vault assets. A custom page is for when you already have a finished, fully custom design and just need somewhere to host it under your brand's rules. In linkable.id you can use both in the same workspace.
If an upload fails validation, for example because the entry file is missing or assets point to the wrong path, the live version of your linkable.id custom page keeps serving and you're told what to fix. If a new version goes live with a bug, you can activate an earlier one in one click.
Yes, as long as you declare them on the page: linkable.id maintains the domains for providers like Google Analytics, Calendly, HubSpot or YouTube, and you can add your own. Forms have to submit to your API or an outside service, since no server-side code runs. In the current mode the page can't store cookies or browser data, and iframe embeds like videos or calendars depend on a mode that is rolling out for public pages only.
Yes. With the linkable.id Claude connector, Claude creates the page, uploads the compiled build and can roll back to an earlier one, up to 10 builds an hour per connection. The page starts private, and publishing it, updating a page that's already public or loosening its sandbox takes a separate permission the user grants.
Do you have campaign pages hosted outside your domain?
Let's go through which ones can move to linkable.id as custom pages and what each one needs to run inside the sandbox.