Multi-tenant API • campaign-orchestrator runtime • real-time metrics

Launch tenant-ready campaign ops with real-time metrics.

A multi-tenant API and runtime for creator campaigns, submissions, payouts, and social connections—built for high-volume clip pipelines with enforced tenant isolation, auditable workflows, and event-ready integrations.

Live now: X, YouTube, Instagram, Facebook. TikTok coming.

Request tenant access View API docs Tenant login

Tenant isolation enforcedEncrypted tokensAudit trail + checksumsAutomated metrics pulls

Show example commands

campaign-orchestrator

$ tenants status --live
12 active tenants · 2 pending verification

$ metrics pull --platform x --limit 50
snapshots: 50 · failures: 0

$ links mint --campaign 7f2c --supporters 214
unique urls minted · ready to share

$ payouts generate --campaign 7f2c
batch queued · 214 lines

$ audit trail --tenant 7c8e
checksum ok · encrypted tokens

Everything is tenant-scoped. Everything is auditable.

24/7Automated metrics pulls

4Supported social platforms

99.9%Tenant isolation enforced

campaign-orchestratorDurable workflow runtime

Tenant-ready campaign primitives (built for scale)

Everything you need to run creator campaigns as infrastructure—not spreadsheets.

Multi-tenant campaign primitives

Tenants, campaigns, assets, submissions, payouts—cleanly separated with role-safe access.

Secure social connections

Scoped tokens per tenant with encryption and predictable lifecycle controls.

Automated metrics snapshots

Scheduled pulls and snapshot history across supported platforms with failure visibility.

High-volume clip pipelines

Designed for large submission throughput and repeatable campaign execution.

Auditability by default

Checksums, durable trails, and traceable actions across sensitive workflows.

Event + webhook ready

Emit events like submission received, post verified, metrics snapshot, payout batch queued.

A platform you build on

Clippers isn’t just a dashboard. It’s a tenant-ready campaign layer you plug into your creator product, loyalty system, or rewards engine.

Bring your own experience

Use your UI, your flows, your branding. Clippers powers the backend ops.

Compose workflows

Campaign creation, approvals, payouts—run as durable orchestration.

Integrate cleanly

Use APIs + webhooks to sync events to CRM, rewards, BI, or your ledger.

View API docs

Your system of action, not another data island

Webhooks for real-time downstream actions
Snapshot exports for BI and reporting
Tenant-level keys and scopes
Idempotent event delivery (recommended)

submission.receivedpost.verifiedmetrics.snapshot.createdpayout.batch.queuedtenant.connection.updated

Tenant isolation isn’t a feature. It’s the floor.

Isolation, encryption, and audit trails are designed into every operation that touches tokens, payouts, or metrics.

Tenant-scoped access controls
Encrypted token storage
Auditable trails for sensitive operations
Durable workflows for payout generation
Separation of tenant data and operational state

Read security overview

Built for teams shipping creator ops

Creator platforms

Run campaigns, submissions, and rewards without rebuilding core ops.

Agencies

Operate multiple client tenants with clean separation and reporting.

Brands with ambassador programs

Track posting behavior, prove attribution, and reward real amplification.

Loyalty and rewards ecosystems

Trigger points, perks, or payouts from verifiable campaign events.

FAQ

Is this a dashboard or an API?

Both. The core is a multi-tenant API and orchestration runtime. You can use the UI or build your own.

What do you track—clicks or posts?

Clippers is designed to track posting behavior and attribution, not just clicks.

How do you handle tenant isolation?

All operations are tenant-scoped. Tokens and sensitive actions are encrypted and auditable.

Which platforms are supported today?

X, YouTube, Instagram, and Facebook are live. TikTok is coming.

How do payouts work?

Payouts are generated as durable batches with audit trails and explicit workflow steps.

Onboarding workflow

Registration is currently manual. Requests are reviewed before tenant provisioning unless an invite code is supplied.

Request access

Submit your company details, intended volume, and platform mix.

Verification

We validate use case, security posture, and growth timeline.

Tenant launch

You receive API keys, JWT secret, and console access.

Request tenant access

We approve new tenants manually. Invite codes skip the review queue.

Note: Requests without an invite code require manual review before a tenant is provisioned.

Build creator ops that scale—and prove it with data.

Request tenant access to launch your first workspace and start tracking campaigns across supported platforms.