in.rt.ht and short links

in.rt.ht opens any deployment through one gateway origin. rt.ht and its sibling hosts serve short links: go.rt.ht opens a new playground, get.rt.ht opens an empty playground that can claim the page you came from, and short paths such as rt.ht/e lead to RTEdge.net, to the feedback repository and to more. The apex rt.ht is the short-link service, not a deployment.

Syntax

plain
https://in.rt.ht/<route>/<path>
https://rt.ht/<short link>
https://go.rt.ht/
https://get.rt.ht/:

Parameters

in.rt.ht Experimental

<route>

The first path segment. A segment without a dot gets .rt.ht, so in.rt.ht/new/ is new.rt.ht. A dotted segment is used as it is, so in.rt.ht/zoo.do/.js is zoo.do/.js.

<path>

The rest of the path, with the query. The route answers it as it would answer a request on its own address.

A trailing ?

A URL that ends in ? is forwarded as it came, so in.rt.ht/<route>/? opens the source like <route>/?. For other URLs, headers whose value contains in.rt.ht, typically Referer and Origin, are removed before the request is forwarded.

Platform suffixes

They still apply. in.rt.ht/new/::u opens the usage dashboard filtered to route:new.

The * index of a deployment links every card through //in.rt.ht/<route>. Domains and subdomains shows where the gateway fits among hosts and routes.

Short links on rt.ht

A short link matches /<prefix> or /<prefix>/…. The rest of the path and the query are kept, unless the link says otherwise.

Short linkOpens

Every redirect is a 307, and HTTPS responses carry HSTS. Except for Remote Output codes, the body is empty text/plain.

Quick starts

https://go.rt.ht/

Redirects to the playground, which runs its code.new action, Create: New Code…, the new-code dialog. It is the target of the "⚡ Start Shipping" link. go.rt.ht is a worker deployment: the root and the /: worker path redirect, and a path that ends in / is a separate route with no deployment.

https://get.rt.ht/:

Redirects to an empty playground. When the request has a Referer, get.rt.ht looks up the referring page's host and opens the playground set up to deploy to that route. The platform's "Code does not exist." page links to get.rt.ht/: as "Deploy your code here" for signed-in visitors. Add rel=noreferrer to your own links to get the empty playground without a pre-set route.

st.rt.ht, sb.rt.ht, bl.rt.ht and code.rt.ht Experimental

st.rt.ht, sb.rt.ht and bl.rt.ht open the same empty playground as get.rt.ht without a Referer, for any path, with the query dropped. code.rt.ht<path and query> goes to https://rtcode.io<path and query>.

CodePen pens Experimental

A path with three or more segments on rt.ht goes to cp.rt.ht, the CodePen importer, so replacing codepen.io with rt.ht in a pen URL opens the pen in RTCode.io. https://rtcode.io/<user>/pen/<id> and https://xcodepen.io/<path> work the same way, and https://cp.rt.ht/ opens the playground's Import URL prompt. The editor's Import URL and Paste URL Content commands rewrite pen URLs to cp.rt.ht for you. Because of this rule, a path with three or more segments is never a prefix link.

Remote Output codes Experimental

A path that starts with digits, such as /123, or any other unmatched path of four or more characters after the slash, such as /abcd, redirects to a remote output on out.rtcode.net. The editor's Remote Output shares its sessions as https://rt.ht/<id>, and its own dialog marks it as work in progress. See Output windows.

Response

URLAnswer
in.rt.ht/<route>/<path>The deployment's own response, with its own headers: edge: o for a root document and edge: oF for an exported file.
A short link on rt.htA 307 redirect with an empty text/plain body. A Remote Output code answers with the body <λ> → <ϟ> and Cache-Control: no-store.
go.rt.ht and get.rt.htA 307 redirect to the playground.

Examples

rel=noreferrer keeps get.rt.ht from pre-setting a deploy route taken from the page that links to it.

html
<a href=//go.rt.ht>⚡ Start Shipping</a>
<a href=//get.rt.ht/: rel=noreferrer>Empty playground</a>
<a href=//rt.ht/e>RTEdge.net</a>
<a href=//rt.ht/gh>Feedback on GitHub</a>
<a href=//rt.ht/?>All short links</a>

Open a deployment through the gateway Experimental

The route maps to new.rt.ht. The second link adds a platform suffix.

HTML

html
<a href=//in.rt.ht/new/>new.rt.ht via in.rt.ht</a>
<a href=//in.rt.ht/new/::u>Usage for new.rt.ht</a>

Result

CORS and limits

Status

The prefix links of rt.ht, go.rt.ht and get.rt.ht are available. in.rt.ht, the Remote Output codes, the CodePen hand-off and the other quick-start hosts are Experimental. Behavior was checked on 2026-10-04.

See also