Feature — Backbone

Every Client Isolated.
Every Event Verified.

Backbone is the multi-tenant infrastructure behind Digenio AI: every client's data lives on its own dedicated server, every tracking event is domain-validated and routed in real time, and the platform scales by adding capacity — never by mixing your data with anyone else's.

Per-tenant database isolation Domain-validated events EU hosting
backbone.digenio.ai — registry console LIVE
Event received — pageview @ client-site.com
uniqueIdTrack: trk_8f3a…91c
IN
Domain validated — matches registry entry
client-site.com → allow · spoofed events rejected
OK
Registry lookup — tenant resolved
tracking_registry → tenant #412 · server: Mars
ROUTE
Written to isolated tenant database
backbone_mars_client412 · visible in dashboards < 1s
ISOLATED

Most SaaS Puts Every Client in One Database. We Don't.

Shared-everything analytics platforms are cheap to run — and expensive to trust. One noisy neighbour, one mis-routed event, one compliance question, and the answer is always "everyone shares the same tables".

The noisy neighbour

On shared infrastructure, one client's traffic spike slows everyone's queries and dashboards. Your reporting shouldn't depend on someone else's campaign going viral.

One incident, everyone affected

When all tenants share one datastore, a data issue is never contained to a single client. Isolation isn't a feature you bolt on — it's how the platform is built.

Unanswerable compliance questions

"Where exactly is our data, and who can touch it?" If the honest answer is "mixed with everyone else's", the deal is already lost. Technical buyers deserve a straight answer.

What Backbone gives you

Infrastructure Built for Scale and Trust

Backbone is the routing and isolation layer every Digenio AI event passes through — built so your data stays yours as the platform grows.

Per-tenant database isolation

Every client gets its own database on a dedicated "planet" shard server. No shared tables, no cross-tenant queries — isolation by architecture, not by promise.

Domain-validated tracking

Tracking events are only accepted from domains validated against the registry — spoofed and unknown-origin events are rejected before they ever touch your data.

Central registry routing

One authoritative registry maps every tracking ID and form ID (uniqueIdTrack / uniqueIdForm) to the right tenant server — added and resolved in real time.

Horizontal scaling

Congratulations, your campaign worked. New servers join the planet pool without downtime, and growing tenants move to bigger shards — the routing layer absorbs the change.

Dedicated endpoints

Tracking and form ingestion run on purpose-built services — backbone.digenio.ai and forms.digenio.ai — separated from the application layer, monitored independently.

EU hosting, GDPR-ready

Infrastructure hosted in the EU, with consent-aware tracking and per-tenant data boundaries that make "where is my data?" a question with a precise answer.

How it works

From Event to Isolated Storage, in Four Steps

Every tracking event and form submission follows the same validated path — no exceptions, no shortcuts.

1

Capture

A visitor lands on your site. The tracking snippet or embedded form sends the event to a dedicated ingestion endpoint — nothing passes through third-party ad networks.

2

Validate

Backbone checks the sending domain against the registry. Events from unvalidated or spoofed domains are rejected — your analytics only ever contains real traffic.

3

Route

A registry lookup on uniqueIdTrack or uniqueIdForm resolves which tenant the event belongs to and which planet server holds its database.

4

Store & serve

The event is written to that tenant's isolated database. On login, your session binds to your server — every dashboard you open reads your shard in real time.

The fleet

A Planet for Every Stage of Growth

Tenants are distributed across dedicated shard servers — each one a "planet" in the fleet, sized for the clients it carries.

Earth

Small clients & startups

Default

Moon

Medium traffic & growth

Scale

Mars

Enterprise & high-volume

Power
New servers join the pool — no downtime Tenants move up as they grow EU hosted
backbone.digenio.ai forms.digenio.ai
Data & integrations

Where Data Comes In, and Where It Goes

Data in

Everything Backbone routes arrives from sources you control — validated at the door.

  • Smart Tracking events — pageviews, sessions, engagement, UTM campaigns — from your validated domains
  • Form submissions captured by embedded Digenio AI forms via forms.digenio.ai
  • Visitor identity — consent-aware first-party cookies that assign each visitor a unique tracking ID

Data out

Your isolated database feeds the platform — and only the destinations you choose.

  • Dashboards and every analysis module — real-time reads from your own shard, never a shared store
  • Enriched lead dispatch to your CRM via the bridge connectors
  • Notification emails and internal alerts, per event pipeline
FAQ

Questions, Answered

In the European Union. All platform infrastructure — ingestion endpoints, shard servers and tenant databases — runs on EU-hosted infrastructure, and tracking is consent-aware with GDPR principles built into the pipeline, not layered on top. In a technical deep-dive we can walk you through the exact setup.
Each tenant has its own database on a dedicated shard server. The Backbone registry maps your tracking and form IDs to your server, and every event is written only to your database — there are no shared tenant tables to leak across. Your dashboards read from your shard, and on login your session is bound to your server.
Events are only accepted from domains validated against the registry and bound to your unique tracking ID. Traffic from unregistered or spoofed domains is rejected before it reaches your database — so your conversion numbers aren't inflatable by bots, competitors or scripts pointing at your tracking ID.
That's the point of the fleet. Capacity scales horizontally — new servers join the pool without downtime — and tenants that outgrow their planet are migrated to a larger shard as part of the service. The registry absorbs the change, so your tracking snippets and forms never need to be re-deployed.
Tenant databases are backed up independently, and because ingestion runs on dedicated endpoints separate from the application layer, incidents in one layer don't take down the other. Concrete backup schedules, monitoring and SLA terms depend on the plan — bring your requirements to the technical deep-dive call and we'll match them.

Stop guessing.
Start knowing.

See exactly which marketing drives revenue —
from first click to closed deal.

Free 7-day trial
GDPR ready