Betsy Active Defense
Enterprise-grade protection for demand intelligence — isolation, access, and data boundaries brands can rely on.
Brand teams need live category demand they can put next to the business — without inheriting someone else’s customers or an amateur data plane. Active Defense is how Coriolis isolates tenants, controls access, and protects data across Brand Intelligence, GunSearchEngine, and the dealer network.
- No shopper emails in BI
- Seller-scoped store data
- Signed access & APIs
Designed for brand confidence
Market intelligence without PII
Full-market demand for brands and platforms — without shopper emails or contact lists in partner feeds.
Dealer isolation
Each store’s demand and leads stay with that seller. Independent retailers are not a free-for-all data pool.
Controlled access
Portal roles, API keys, and plan-gated lookback and export. Depth is intentional — not an open warehouse.
Integrity of signals
Product answers ground in live catalog tools. Payment webhooks are signature-verified. Production ships through CI.
Built on proven infrastructure
Production applications, edge protection, managed data, and continuous integration — vendors you can name, operated as one platform.
Application hosting
Vercel
GunSearchEngine and GunSearchAgent run as Next.js applications with TLS, environment secrets, and production deploys from protected branches.
Source & CI
GitHub
Private repositories, pull-request workflow, and continuous integration on main — including platform integrity checks before release.
DNS & edge
Cloudflare
DNS and edge protection in front of public surfaces for traffic hygiene and resilience at internet scale.
Managed Postgres
Neon
Application data in managed Postgres with connection security and backups as part of the data plane.
Operations
Monitoring
Runtime visibility, structured logs, and public platform status so availability and abuse stay observable.
Verified webhooks
Stripe
Billing and merch events verify Stripe signatures. Separate webhook secrets for GunSearchAgent and GunSearchEngine.
How isolation works
Four lines of defense — written for brand and security stakeholders, enforced in product.
Isolate
Multi-tenant by design. Store intelligence is seller-scoped. Brand Intelligence receives anonymized market patterns — not a dump of dealer customer lists.
Authenticate
Signed sessions for Brand Intelligence, dealer portal, and platform admin. API keys for OEM integrations. Server-side secrets never ship in the browser.
Authorize
Every sensitive path checks who may see which client, seller, or export depth. Support access is time-bounded and scoped to the store being helped.
Protect data
HTTPS on public surfaces. Encrypted dealer CRM credentials. Rate limits on public and partner APIs. Shopper PII kept off OEM export paths by product design.
How real-world attacks are contained — and brand data stays isolated.
Always on
Changes move from GitHub through continuous integration into Vercel. Integrity checks fail the pipeline when platform contracts drift. Rate limits and authentication protect public and partner APIs. Platform status keeps operational health visible.
One platform. Clear boundaries.
Brand Intelligence
Private portal and REST API for manufacturers — full-market demand with plan-gated depth and no shopper emails.
GunSearchEngine
Multi-dealer discovery, embed runtime, Insights, and the APIs that power Brand Intelligence.
GunSearchAgent
Dealer accounts and store-scoped demand — isolated tenancy for the independent channel.
My Betsy
In-store edge shell. No local customer database; intelligence stays in the cloud platform.
FAQ
FAQ
- Do brands receive shopper emails?
- No. Brand Intelligence is built on anonymized demand patterns — what people asked for across the network, not who they are. Partner APIs and exports are designed without shopper emails or session identifiers.
- Can another brand or store see our private data?
- Store demand and dealer portal data are scoped to the owning seller. Brand Intelligence clients access market intelligence under their account and API keys — not another OEM’s workspace or a dealer’s private CRM.
- How is access controlled?
- Brand Intelligence uses portal authentication, team roles, and secure API keys. Lookback, sessions, and export depth follow your plan. Dealer accounts on GunSearchAgent are separate from platform admin and from OEM portals.
- Where is the platform hosted?
- Applications run on Vercel. Source control and CI are on GitHub. DNS and edge protection use Cloudflare. Application data is in managed Postgres (Neon). Monitoring and platform status support day-to-day operations.
- Do you provide SOC 2 or pen-test reports?
- Active Defense describes how the live platform is designed and operated. Formal attestation packages vary by stage of the business. For security questionnaires or current documentation, contact Coriolis — we will share what is available and map controls to your review.
- What if a dealer embed key is compromised?
- Site keys bind embed traffic to the correct store. Contact Coriolis support to rotate and invalidate a key. Origin expectations further limit where web embeds are intended to run.
Ready for Brand Intelligence
Private dashboard and API for full-market 2A demand — on a platform designed for multi-tenant isolation and brand-grade data boundaries.