Quickstart

Go from an empty Spaceflare account to a connected server and Cloudflare account, then attach your first product, all from the dashboard.

Last updated

On this page

This quickstart takes you from a fresh account to a working setup in a few minutes: connect a server, connect a Cloudflare account, then attach a product to either one. Everything happens from the Connector page (the dashboard home). There is nothing to configure by hand.

Before you start

You need an Spaceflare account. For the server path you need a Linux server with root (or sudo) access; for the Cloudflare path you need a Cloudflare account with at least one zone. Products you bought appear in the sidebar, grouped by category. If one is missing, open a ticket from My tickets and we will attach it.

1. Connect a server with Server OAuth

Servers join the platform through the open-source xdpd fleet daemon. One command installs it:

  1. Open the Connector page and click Add server on the Server OAuth card. The Add a server modal mints a one-time enroll token and shows the install command.
  2. Run the shown command as root on your server. It installs the daemon as a systemd service, which enrolls itself and starts reporting.
  3. Keep the modal open. It flips to Server enrolled as soon as the daemon checks in, usually within seconds. The server now reports every 15 seconds and appears on the Connector page and in Health Monitor.

The daemon only reports health and runs installs you approve. Removing the server from the console later uninstalls the daemon with one click.

2. Connect a Cloudflare account

  1. On the Connector page, click Add Cloudflare on the Cloudflare OAuth card, then Connect with Cloudflare.
  2. Approve the access on Cloudflare. You are redirected back and the account appears on the Cloudflare OAuth card. We never see your password.

No OAuth? The same modal takes an API token below the or use an API token instead divider: give the connection a label and paste a token from dash.cloudflare.com/profile/api-tokens (a zone-scoped token is fine). The token is validated against the Cloudflare API before saving and stored encrypted.

3. Attach a product

Every product page lives under /dashboard/products/<name> and picks from the connections you just made. The common first moves:

  • OpenShield-XDP: open your server's Products tab and click Install, or use Install on a server on the product page. The licensed wizard installs the kernel firewall with no shell work; watch it stream live.
  • LiteShield-XDP: same idea, lighter agent: use the install section on the product page for a fleet server, or Add server to register a box already running it with its API URL and lsk_… key.
  • Health Monitor: nothing to install: click the server on the Connector page's Server OAuth card for its health score, resources, VMs, events and benchmarks.
  • Web Firewall: click Connect a domain on the product page: pick a Cloudflare zone, set the hostname and origin backends, and the DNS cutover is handled for you.
  • L4 Tunnel: click New tunnel on the product page and pair two connected servers: a public origin in front of a hidden destination.
  • Game Panel Setup: click Install on a server on the product page, pick an online server, and answer the wizard. The panel installs with TLS and streams every step live.
  • Server Optimization: click Install on the server's Products tab, or start a New run on the product page and paste the one-line command on any server.
  • Cloudflare Analytics: click Attach zone on the product page; each attached zone holds one seat.
  • Cloudflare WAF Setup: open a connection's zones on the product page and protect one; a snapshot is saved before anything is applied, so rollback is one click.

Next steps