Shareable routes
Vanity Domains
Vanity domains make public Vibecodr work easier to share without changing the underlying source, runtime, or visibility rules.
Vanity domain guide for Vibecodr vxbe.space public routes.
Implementation focus
Use this when claiming a `vxbe.space` name, changing targets, debugging hosted attribution, or deciding whether a vanity route should follow a live app.
Expected outcomes
- Understand what vanity domains can point at.
- Know how plan limits and watermark behavior affect routes.
- Release unused names intentionally.
- Troubleshoot routing without confusing vanity with source or runtime state.
Vanity names live on vxbe.space
A vanity subdomain gives a vibe, post, or supported Pulse target a cleaner `vxbe.space` route. It is a public routing convenience, not a new security boundary and not a way to bypass visibility, embed, or source rules.
Plans limit how many vanity names an account can hold. Free vanity routes keep hosted attribution, while paid plans can remove the hosted watermark where the product allows it.
- Claim names that match real projects or public identities.
- Release unused names when the project no longer needs them.
- Expect inactivity release rules to prevent long-term squatting.
- Use public metadata so the vanity route still explains what viewers are opening.
Troubleshoot vanity routing
If a vanity route does not open the expected experience, check the target type, visibility, latest release, and whether the name is still attached. If an embedded vanity route behaves differently, check embed policy in addition to vanity routing.
A vanity route can make a project easier to share, but it does not change the underlying source, artifact, Pulse, or plan limits. Fix the underlying target when the route points to a broken or unpublished app.
- Use BUMP IT when the vanity route should keep following the same app identity.
- Use exact artifact links when a third-party page must stay pinned.
- Check watermark behavior against the current plan.
Example and read next
Example: you want a cleaner URL for a live app. Claim a vxbe.space name, point it at the supported target, confirm watermark behavior for the plan, and release it if the project goes inactive.
Use these related pages when you need the next layer of guidance. They point to the most likely follow-up tasks, not every page that happens to touch the same system.
- Read next: /pricing
- Read next: Embeds
- Read next: BUMP IT
- Read next: Troubleshooting