Intelligence is the per-brand context layer. Veeva runs both directions: approved content out to PromoMats, performance back from CRM. Your own properties — kiniksa.com, Compound DT-204.com, claims library, ISI library — index into Intelligence so every output reads on-voice and stays in-label. Ad platforms close the performance loop back to the index.
Architecture · Layer 01 · Source of truth
This is Intelligence — per-brand RAG. Approved claims, label facts, prior MLR-cleared creative, competitor watch. Cited on every output.
Across Demo Therapeutics properties + Veeva + ad platforms
Items in brand brain
8,420
+312 this week
Claims, ISI passages, press, study citations
Veeva sync · health
✓ Live
Last sync 4 min ago
PromoMats + CRM both bidirectional
Scrape coverage
94%
13 of 14 sources fresh
kiniksa-investors.com queued for re-scrape
Data privacy posture
No PHI ever enters OVYN. Demo Therapeutics keeps the patient-level data wall.
Veeva CRM sits inside Demo Therapeutics's HIPAA-compliant environment. What flows from Veeva into OVYN is already de-identified before crossing the boundary — minimum cohort of 25, no PHI, no PII, no patient-level records. We see what performed, not who experienced it. That makes OVYN a non-covered entity by design — no BAA needed because no PHI ever crosses.
What stays on Demo Therapeutics's side
Patient-level Veeva CRM records
HCP names + practice + prescribing history
Any field that could re-identify
All HIPAA-protected health information
What crosses to OVYN
Aggregate engagement (open / click / view) by audience cohort
Cohort minimum: 25 records — below threshold, the row drops
MLR review outcomes (flag / approve patterns), no reviewer attribution
14 fields total · no PHI · no PII
For your security review · OVYN runs on SOC 2 certified infrastructure (Anthropic, Vercel, Twilio). HITRUST-aligned data-handling practices. DPA available on request. Subprocessor list disclosed up front. No client data is used to train foundation models. Demo Therapeutics-specific Veeva connector built during onboarding with sandbox-first validation before any production data movement.
Flagship integration
Veeva — PromoMats + CRM, both directions
Approved content flows out to PromoMats on MLR approval. De-identified engagement data flows back from CRM nightly. The MLR review history trains the pre-check rail. We work alongside Veeva — not around it.
● Connection healthyOAuth 2.0 · auto-refresh
→
OutboundPromoMats · compliance archive (system of record)
On MLR approval, every variant auto-archives to PromoMats with full metadata so Veeva stays your authoritative compliance record. PromoMats is your archive — OVYN handles the publishing to Meta, IG, TikTok, LinkedIn, email, and ad networks. Note: the Veeva connector itself is built as part of Demo Therapeutics onboarding — typical scope, 4–6 weeks, with sandbox-first validation before production.
· Lockstep: deployment events on Meta/IG/TikTok/LinkedIn write back to the PromoMats record so the archive reflects where each asset actually ran
● healthy
Real-time on approval Last: Configured during onboarding
Volume scales to whatever Demo Therapeutics pushes
←
InboundVeeva CRM · HCP engagement signal
De-identified, aggregate engagement data from Veeva CRM flows back as performance signal — open rates, click-throughs, rep-triggered content performance per audience segment. Configured during onboarding alongside the PromoMats connector. Cohort minimums and field-level scope reviewed with your privacy team before any data moves.
· Aggregation: Min cohort 25 to prevent re-identification
· No PHI / No PII fields ever ingested
· Used as signal in: Performance loop, top/bottom-25% analysis
● healthy
Nightly batch (configurable) Last: Configured during onboarding
Sample volume only · scales with Demo Therapeutics data
←
InboundVeeva PromoMats · MLR review history
Historical review records — what got flagged, what got approved on first pass, redline patterns by reviewer. Trains the pre-check rail. Optional ingest, scoped during onboarding.
· Trains the OPDP rail's auto-flag logic
· Reviewer-pattern tuning is opt-in
· No reviewer attribution in outputs
● healthy
Weekly batch (configurable) Last: Configured during onboarding
Sample volume only · scales with Demo Therapeutics data
Brand brain · own-source ingestion
Demo Therapeutics properties feeding the model
Every Demo Therapeutics-owned surface is scraped on a schedule. Pages turn into structured snippets — claims, citations, audience scope, ISI variants — that the engine retrieves at generation time. Add a URL, set a cadence, the brain learns it.
Source
Type
Items
Last scraped
Cadence
Status
kiniksa.com
Pipeline pages, leadership bios, press, financials. Used for corporate context + DT-387 messaging consistency.
AHA, ACC, EULAR abstracts and posters citing Compound DT-204 or rare cardiology indication. Trial-cited claims library expansion.
Scientific
28
3 days ago
Weekly
✓ fresh
kiniksa-investors.com
Investor relations content. Currently queued for re-scrape — last attempt got rate-limited. Re-running tonight.
Investor site
24
5 days ago
Weekly
queued
How it works · Each scrape hits the source, extracts structured snippets (claims, citations, audience scope, ISI variants), tags them with audience + indication + freshness, and writes to the brand brain index. Every variant the engine produces retrieves the relevant snippets at generation time — so a caregiver carousel always cites a real, current, in-scope claim, not a hallucination.
OVYN-deployed channels
What we publish directly · social, email, owned web
Once a version clears MLR and lands in your Veeva archive, OVYN auto-publishes it to every social channel you've enabled, your SFMC email, Reddit, and your owned web properties. Same approved asset, fanned out to every place it's supposed to run, with channel-specific format conversion automatic.
✓ 18 deployments · last 24h
Meta · Instagram + FacebookSocial · paid + organic
Direct publish via Graph API. Paid runs through Business Manager — same creative, ad-targeted to caregivers, newly-diagnosed, and HCP-adjacent audiences.
Bidirectional. eBlast HTML + banners auto-pushed to SFMC content library, then scheduled or triggered. Open/click signal flows back to Performance loop.
eBlastEmail bannerTriggered drip
● connected
Triggered + scheduled sends
2 sends scheduled
Reddit · paid + communityCommunity-targeted
Targeted to r/cardiology adjacent + autoinflammatory community subreddits. Native promoted posts only — no banner-style display.
Promoted postConversation ad
● connected
Live · 1 active campaign
2 native posts queued
Compound DT-204.com CMSOwned property · direct publish
Available if Demo Therapeutics enables headless publishing on Compound DT-204.com — direct publish via API, same compliance rail (pages don't go live until MLR-approved).
Long-form pageFAQCaregiver hubISI block
● connected
Auto-publish on approval (when CMS API is enabled)
1 page queued
Media agency handoff
Programmatic, video paid, search · your agency buys, we feed and report
We don't buy media. Your media agency does — CMI, Real Chemistry, whoever's on retainer. Our job is to hand them MLR-approved files + spec sheets through their preferred portal, then pull their raw performance data back via API so the same dashboard shows social + email + media-agency numbers in one view. The current connection prevents the report-discrepancy problem where your platform numbers and your agency numbers drift apart.
CMI Media · default partner
Programmatic display + nativeProgrammatic · paid
MLR-approved creative + spec sheet handed off to your media agency through their preferred portal (CMI Media, Real Chemistry, etc.). They run the buy. Raw performance data pulls back to OVYN via the agency's reporting API.
Your media agency runs the YouTube + connected-TV buy. We supply the MLR-approved cuts (60s / 30s / 15s / 6s bumper) — they handle placement, frequency capping, and brand-safety controls. Raw data flows back into the Performance loop.
TrueViewBumper · 6sIn-stream skippableCTV / OTT
→ Agency portal← Raw perf via API
Search · Google + BingPaid search
Search ad copy + extensions go to your media agency for upload to Google Ads / Bing. They manage bidding, keyword strategy, and quality score. We supply the MLR-cleared headline/description matrix.
Connection guarantee · The performance-data API pulls hourly from your media agency's reporting platform. If your agency reports different numbers later, you'll see ours update in lockstep — no drift, no after-the-fact reconciliation. Want a different agency partner? Tell us during onboarding; the connector covers Publicis Health, Real Chemistry, Klick, Indegene, Ogilvy Health, and any agency running standardized export feeds.
Live activity
Deployment + archive · last 24 hours
Each approved variant fans out to every destination channel and lands a compliance record in Veeva — in parallel. One approval, every channel, one archived record.
12 min ago
DEM-2026-04-218
Caregiver carousel · 'When you knew it wasn't a heart attack'
MetaIG + FB feed organic + paid
VeevaPromoMats v2 archived
47 min ago
DEM-2026-04-217
RP awareness reel · physician POV · 36s
MetaIG paid · cardiology lookalike
YouTubeTrueView · 4 audience cohorts
VeevaPromoMats v1 archived
2 hr ago
DEM-2026-04-215
What is rare cardiology indication · 60s explainer
Google AdsDisplay banners · 4 sizes · live in rotation
Compound DT-204.comCost & access page updated
VeevaPromoMats v3 archived
Performance closure · read-only
Analytics that close the feedback loop
Once content is live, these read-only connectors stream engagement, conversion, and cost-per-action back into the Performance loop. The system knows which variants actually performed in the wild — not just which ones cleared MLR.