Skip to content

Beta · Justikail is free during beta.

justikail

REV beta MODULE GSocket

Your server has no public address.
Open a shell anyway.

Your server dials out to a relay and meets your browser there. Nothing to forward, no inbound rule to add, no public IP to buy.

Free during beta · for servers you own or are authorised to access.

FIG. 1 — reach path
firewall your browser relay your server wss · TLS single-use token · 30s outbound only no inbound port
$ uptime
 14:02:11 up 41 days,  3:22,  1 user
$ 

How it works

Three steps, no network changes on your side.

  1. 01

    Add a connection

    Give it a name and paste the GSocket secret. It is encrypted before it is stored, and never sent back to your browser.

  2. 02

    Press connect

    Justikail authorises the request and issues a short-lived, single-use token for that one session.

  3. 03

    Work in the terminal

    An interactive shell opens in your browser. Close the tab or hit disconnect and the session is torn down.

Built for access you can trust

Encrypted secrets

Connection secrets are encrypted at rest and never sent to the browser, returned by the API, or written to logs.

Per-user isolation

Every connection is scoped to its owner and checked at multiple layers. No account can reach another account's servers.

Timeouts & limits

Idle and maximum-duration timeouts end forgotten sessions, with a cap on concurrent sessions per account.

Audit log

Who connected to what, and when. Metadata only — terminal contents are never recorded.

Real web terminal

A full interactive shell in the browser, with resize and copy/paste, backed by a real PTY.

No port forwarding

Your server reaches out through a relay, so you never expose an inbound port or edit firewall rules.

Security is the product

A tool that opens a shell has to earn trust. These are the controls we build around that, and we would rather over-explain them than ask you to take them on faith.

  • Secrets encrypted at rest, decrypted only in memory at connect time.
  • Strict tenant isolation — enforced at the query, policy, token and connection layers.
  • Administrators cannot open a terminal or decrypt a secret belonging to another account.
  • Restricted egress: the terminal service can only reach the relay network.
  • Audit logs record session metadata, never terminal contents.

Free while we are in beta

Every plan is free today. The pricing page shows the limits each tier will carry, so there are no surprises later.

Compare plans

Frequently asked questions

Is Justikail free?
Yes. Justikail is free during beta and no plan is billed today. Paid plans shown on the pricing page describe where the product is heading.
Do I need to open a port on my server?
No. Your server connects outbound to a relay, so there is no inbound port to open and no firewall rule to change.
Can Justikail staff read my terminal session?
No. Terminal contents are never stored. We keep session metadata for auditing, and administrators cannot open a terminal or decrypt a secret belonging to another account.
Where is my connection secret stored?
Encrypted at rest, and decrypted only in memory at connect time — by the terminal service, never by the web app. It is never sent to your browser, returned by the API, or written to logs.
Can I use this on servers I do not own?
No. Justikail is for systems you own or are explicitly authorised to access. Anything else violates our acceptable use policy.

Open a terminal to your own server

No credit card, no port forwarding. Free during beta.

Start free