BYOC

Run mobile attribution in your own cloud

Q: What is Linkrunner BYOC?

Linkrunner BYOC runs the mobile attribution data plane inside your cloud while Linkrunner handles updates, agent orchestration, metering, and support through a scoped control plane.

Q: Does raw attribution data leave our cloud?

No. Raw events, identifiers, and PII remain in your cloud boundary. The control plane receives health signals and aggregate usage counters for operations and billing, never user-level attribution data.

Q: Who pays for the infrastructure?

You provision and pay for the data-plane infrastructure in your own cloud account. Linkrunner charges for the metered agent layer that reads and acts on that local attribution data.

Q: Does BYOC bring attribution cost down to zero?

It brings Linkrunner's BYOC data-plane attribution fee to $0 per attributed install. You still pay your own cloud infrastructure, and optional managed agents are metered separately.

Q: Where do agents execute?

Agents execute inside your data plane. Linkrunner manages definitions, prompts, attribution models, fraud rules, integrations, and policies, then pushes scoped config at run time.

Q: Which clouds are supported first?

GCP is the launch target. AWS support is planned around MSK and account-local inference, with Azure later.

Keep raw events, identifiers, and PII inside your account. Linkrunner keeps the deployment and agent workflows running.

Get in touch

Full control

Remove the attribution burden from your marketing budget

Spend more on user acquisition than tracking

Linkrunner · BYOC

Attribution cost receipt

Attribution platform fee

per attributed install on the BYOC data plane

Cost owner

infrastructure spend stays visible in your account

Cloud bill

Budget impact

measurement fees stop eating into acquisition spend

More media

Measure installsBuy more users

Data plane

Bring Linkrunner's data plane into your stack

Use your own stores and network policy while keeping the mobile attribution workflow your growth team needs for campaign reviews.

Postbacks

Installs

Clicks

SKAN

Fraud

Protect

Revenue

Sync

Postbacks

Installs

Clicks

SKAN

Fraud

Protect

Revenue

Sync

Postbacks

Installs

Clicks

SKAN

Fraud

Protect

Revenue

Sync

Postbacks

Installs

Clicks

SKAN

Fraud

Protect

Revenue

Sync

Postbacks

Clicks

SKAN

Fraud

Protect

Revenue

Sync

Postbacks

Installs

Clicks

SKAN

Fraud

Protect

Revenue

Sync

Postbacks

Installs

Clicks

SKAN

Fraud

Protect

Revenue

Sync

Postbacks

Installs

Clicks

SKAN

Fraud

Protect

Revenue

Sync

Postbacks

Installs

Clicks

LR Config

Boundary contract

Your data stays with you. Linkrunner keeps it running.

Only scoped configuration enters your cloud. Only health signals and aggregate usage counters come back.

Your cloud

Data plane

Clicks, installs, events, revenue, postbacks, and agents run inside your account.

Raw events, identifiers, and PII stay in your boundary.
Each deployment is single-tenant for your team or project.
You own the cloud account, stores, and network policy.

Linkrunner

Control plane

Linkrunner manages updates, models, fraud rules, integrations, metering, and support without raw attribution rows.

Scoped agent configuration flows into your cloud.
Only health signals and aggregate usage counters flow back.
Every boundary crossing is logged and auditable.

Agents

Agents work where your data lives

Ask questions, catch issues, and approve optimizations without moving attribution context.

Tier 1

Analyst agents

Answer campaign questions, flag anomalies, and send digests.

Tier 2

Optimization agents

Suggest budget, pacing, bid, and integration fixes for approval.

Adoption path

Review to autonomy

Start read-only, add approvals, then grant scoped autonomy.

Security

Residency is enforced by the deployment shape

The control plane can operate Linkrunner without receiving raw attribution rows, user identifiers, or model context.

Linkrunner compliance

Trust Center

AICPA SOC 2 Type 2

GDPR

ISO 27001

Raw attribution data and PII never leave your VPC.

The control link is scoped, auditable, least-privilege, and revocable.

Data is encrypted in transit and at rest with your KMS.

Every agent action and boundary crossing lands in an immutable audit trail.

Enterprise deployments support RBAC and SSO for operator access.

Linkrunner

Fast managed launch.

BYOC

Strict residency or cloud-control needs.

Linkrunner compared with Linkrunner BYOC
Area	Linkrunner	Linkrunner BYOC
Data location	Linkrunner-managed cloud.	Your cloud account.
Deployment shape	Managed SaaS.	Single-tenant data plane in your account.
Operations	Infra, releases, monitoring, and support.	Scoped, auditable control link.
Models, rules, integrations	Managed by Linkrunner.	Managed by Linkrunner, pushed as scoped config.
Pricing	$0.01 per attributed install.	$0 per attributed install for the BYOC data plane.
Infrastructure cost	Included in the managed service.	You pay your cloud infrastructure.
Agents	Run on Linkrunner-hosted data.	Run in your data plane.
Best fit	Fast managed launch.	Strict residency or cloud-control needs.

Frequently asked questions

How Linkrunner BYOC handles data residency, agents, and billing.

What is Linkrunner BYOC?

Does raw attribution data leave our cloud?

Who pays for the infrastructure?

Does BYOC bring attribution cost down to zero?

Where do agents execute?

Which clouds are supported first?

Keep mobile attribution data inside your cloud

Bring your account, your network policy, and your data boundary. Linkrunner runs mobile attribution and agent workflows around it.

Get in touch