Veras

Connect every trust signal.

Veras brings events from your moderation, identity, fraud, payments, support, and internal systems into one place, so you can review accounts, trigger workflows, and take action without writing custom glue code.

Book a demoView docs
Pipeline CanvasActive
Ingested Signals
Hivecontent.flagged
Streammessage.reported
Personaverification.failed
Stripechargeback.created
+ 3 more signals
Veras Hubprocessing
01Receive
02Link
03Group
04Route
subject: creator_123
Triggered Actions
Review case
Account timeline
Human review
Hold payout
+ 3 more actions
The problem

Your stack is fragmented

Critical events are scattered across dozens of services.

HiveDISCONNECTED

knows about content.

PersonaDISCONNECTED

knows about identity.

StripeDISCONNECTED

knows about payments.

ZendeskDISCONNECTED

knows about support.

Veras connects those events in real-time.

Product

One event stream. Useful outputs.

Connect the systems you already use. Turn their fragmented events into context your team and products can use.

[01]

Account timeline

See moderation, identity, payment, support, and internal events in one chronological view.

content.flaggedverification.failedpayout.changed
[02]

Prepared review cases

Collect the relevant account history before someone begins a review.

Linked subjectRelated signalsAudit context
[03]

Workflow triggers

Send accounts to the right queue, team, webhook, or internal service.

Route to queueNotify teamSend webhook
[04]

Account actions

Ask your systems to hold payouts, require verification, limit messaging, or apply custom restrictions.

HoldRestrictEscalate

Actions are executed through your own systems. Your team keeps the final decision.

Integrations

Connect events from across your stack.

Use connectors and webhooks to bring vendor and internal events into the same account context.

Moderation

01
  • Hive
  • Stream
  • ActiveFence
  • Custom models

Identity and KYC

02
  • Persona
  • Veriff
  • Alloy
  • Internal verification

Fraud and payments

03
  • Stripe
  • Sardine
  • Sift
  • Internal ledgers

Support and internal

04
  • Zendesk
  • Salesforce
  • Admin tools
  • Custom webhooks
A concrete example

Three signals. One creator. One review-ready case.

  1. 1
    T+0.00s

    Persona reports a failed verification.

    verification.failed
  2. 2
    T+0.08s

    Stripe reports a payout change.

    payout.changed
  3. 3
    T+0.15s

    Hive flags a new upload.

    content.flagged
  4. 4
    T+0.22s

    Veras links all three events to creator_123.

    events.linked
  5. 5
    T+0.24s

    Veras prepares a review case.

    case.created
  6. 6
    T+0.31s

    Platform receives a webhook.

    webhook.sent
  7. 7
    T+1.45s

    Reviewer chooses the next action.

    human.review
For developers

One consistent interface for every event.

Send different vendor events through the same small API. Attach them to the same subject, then build on the connected history.

Use your own subject IDs
Keep the source payload
Add new event types without changing the core model
events.tsTypeScript
await veras.events.ingest({
type: "verification.failed",
subject: {
type: "creator",
id: "creator_123"
},
source: "persona",
occurredAt: new Date().toISOString(),
data: {
inquiryId: "inq_456"
}
});
await veras.events.ingest({
type: "content.flagged",
subject: {
type: "creator",
id: "creator_123"
},
source: "hive",
occurredAt: new Date().toISOString(),
data: {
category: "suspected_deepfake",
confidence: 0.94
}
});
Use cases

Built for platforms

01Creator platforms
02Adult platforms
03Gambling
04Marketplaces
05Dating
06Gaming
Build on Veras

Stop stitching your trust stack together by hand.

Connect your existing tools and turn fragmented events into review-ready context and usable workflows.

Book a demoView docs