Platform
ScaiWave ScaiGrid ScaiCore ScaiBot ScaiDrive ScaiKey Modellen Tools & Services
Oplossingen
Organisaties Ontwikkelaars Internet Service Providers Managed Service Providers AI-in-a-Box
Kenniscentrum
Ondersteuning Documentation Blog Downloads
Bedrijf
Over ons Onderzoek Vacatures Investeren Contact
Inloggen

Quickstart

This walks through the smallest useful deployment: two connectors, one published service, one policy. Fifteen minutes if your egress is already open.

The endpoint names below are provisional. api.proxility.scailabs.ai and *.edge.proxility.scailabs.ai do not resolve yet — the control plane is not generally available (see the status table on Proxility). Nobody should spend an afternoon debugging DNS for a service that has not launched. Correct these names here the moment the real ones exist.

Before you start#

  • A Proxility tenant and a realm. If you have neither, ask your administrator or see Tenants and realms.
  • Two networks, each with a Linux host that has outbound access to *.edge.proxility.scailabs.ai on UDP/443 (TCP/443 is the fallback).
  • The proxility CLI on your workstation.
bash
1
2
3
curl -fsSL https://downloads.scailabs.ai/proxility/install.sh | sh
proxility login            # opens a browser, authenticates via ScaiKey
proxility realm use acme/prod

1. Install the connector in the first network#

On the host inside your data centre:

bash
1
2
3
# Create the enrolment token on your workstation, not on the host
proxility connector create dc1 --description "Amsterdam DC, rack 4"
# → enrolment token: ptk_... (valid 60 minutes, single use)

Then on the host:

bash
1
2
3
curl -fsSL https://downloads.scailabs.ai/proxility/install.sh | sh
proxility-connector enrol --token ptk_...
systemctl status proxility-connector

The connector generates its own keypair during enrolment. The private key never leaves the host — the token only proves the host is allowed to ask for a certificate. Check in:

bash
1
2
3
proxility connector list
# NAME  IDENTITY                     EDGE        STATE
# dc1   prox://acme/prod/dc1         nlwest-std  connected

2. Install the connector in the second network#

Same two steps, different name:

bash
1
2
3
proxility connector create aws-prod --description "AWS eu-west-1, prod account"
# on the cloud host:
proxility-connector enrol --token ptk_...

3. Publish a service#

Services are published by the connector that can reach them locally:

bash
1
2
3
4
proxility service create payments \
  --connector dc1 \
  --target 10.20.4.17:8443 \
  --protocol tcp

That service is now named payments.prod.acme.prox. It is not yet reachable by anyone.

4. Allow one thing#

Default deny means nothing happens until you say so:

bash
1
2
3
4
5
proxility policy allow \
  --from prox://acme/prod/aws-prod \
  --to payments.prod.acme \
  --ports 8443 \
  --description "prod API reaches the payments gateway"

5. Use it#

From the cloud host:

bash
1
curl -v https://payments.prod.acme.prox:8443/health

Name resolution happens inside the connector's split-horizon resolver; see Services and DNS. The TLS session your client negotiates is your own, end to end to the target — Proxility's encryption is underneath it and does not terminate yours.

6. Watch the decision#

bash
1
2
proxility log tail --follow
# allow  prox://acme/prod/aws-prod → payments.prod.acme:8443  rule=prod-api-to-payments  12ms

A denied attempt looks like this, and names the absence of a rule rather than failing silently:

scdoc
1
deny   prox://acme/prod/dev-laptop → payments.prod.acme:8443  reason=no_matching_rule
  • Policy — how rules are written and evaluated, and why they are checked twice
  • Connect a network — production deployment: redundant connectors, sizing, upgrades
  • Cryptography — what actually protects the session
Updated 2026-11-08 18:08:53 View source (.md) rev 3