Cloud Deployment

Overview

tracio.ai is a fully managed cloud platform. Your application sends signals from the browser, and the cloud returns an identification result. The platform handles scaling, redundancy, and infrastructure management.

Getting started takes minutes: create an account, get your public key, install the SDK, and start identifying visitors.

Managed cloud only. TRACIO does not ship a self-hosted or on-premise deployment — there is no installable server component. What you can control is the data region your traffic is served from (see below) and, if you want the agent served from your own domain, a first-party proxy in front of the managed endpoint via the endpoint / scriptUrl options.

How It Works

Your application talks to the cloud through the client-side JavaScript SDK. The SDK loads an agent in the browser, collects signals, and returns the identification result:

Browser (JS SDK)  ──▶  tracio.ai Cloud
                  ◀──  (identification result)

1. The browser SDK loads the agent and collects signals.
2. The signals are sent to the tracio.ai cloud.
3. The cloud returns the result: visitorId and bot info.

To act on results on your own server, receive each identification as a signed webhook, or read them on demand through the Server API.

Getting Started

1. Sign up and open your dashboard.
2. Choose your data region (see below).
3. Copy your public key — it's safe to ship in client-side code.
4. Install the SDK and initialize it:

import { Tracio } from "@tracio/sdk"

const tracio = Tracio.init({
  publicKey: "5ca175fc...",
  region: "eu",
})

Data Regions

The SDK region option selects which data region the SDK talks to. It accepts "us" or "eu". When unset, the SDK uses the generic https://edge.tracio.ai endpoint — set it explicitly to pin a region.

API Key Management

Your workspace uses two kinds of key, and they are not interchangeable:

• Create and manage both in the dashboard under API Keys. Secret keys require the Pro plan or higher.
• A secret key is shown once, at creation — only a hash is kept on our side. If you lose it, rotate rather than recover.
• Rotating a secret key keeps the previous one working for 7 days so you can deploy without downtime. Public keys are not rotatable: they are not secrets, and they are visible in your page source by design.

To consume results server-side you have two options, and they combine well:

• Configure a webhook — each identification is delivered to your endpoint, signed with X-Tracio-Signature.
• Call the Server API with your secret key to read a visitor's history, individual sessions, or velocity counters on demand.

Webhooks

You can configure webhooks to receive identification events from the cloud on your own server. Webhooks are available on the Pro plan and above — see Webhooks for setup, payload and signature-verification details.