Integrations
Integration Readiness
WarpIntel keeps public tools usable while private EVE data, payments, ads, email, Discord, AI, and monitoring integrations stay behind feature gates until each provider lane is reviewed and ready.
External, infrastructure, and production support lanes tracked for launch.
Services safe to rely on in the current public MVP.
Approval, feature-flag, credential, or setup lanes still intentionally held back.
Provider or human-verification lanes not yet ready for public activation.
Integration Action Queue
7 gated integration actions remain, including 3 waiting on provider, account, or verification review and 5 tied to EVE, revenue, or communications launch lanes.
#1 / Revenue And Growth
AdSense
- Public State
- Waiting
- Owner Category
- Provider or account review
- Next Step
- Finish Google verification and keep ad slots hidden until publisher and slot IDs are approved.
- Launch Impact
- Cannot activate public provider behavior until verification or approval clears.
#2 / Comms
Discord
- Public State
- Waiting
- Owner Category
- Provider or account review
- Next Step
- Complete Discord app verification, then validate the signed interaction endpoint.
- Launch Impact
- Cannot activate public provider behavior until verification or approval clears.
#3 / Comms
Resend
- Public State
- Waiting
- Owner Category
- Provider or account review
- Next Step
- Wait for approved sending provider or fallback before enabling transactional sends.
- Launch Impact
- Cannot activate public provider behavior until verification or approval clears.
#4 / EVE Private Data
EVE SSO
- Public State
- Staged
- Owner Category
- WarpIntel setup verification
- Next Step
- Enable public EVE login only after callback, scope map, and live test gates are ready.
- Launch Impact
- Staged for final configuration, link validation, or smoke testing.
#5 / Monitoring
Sentry Error Monitoring
- Public State
- Staged
- Owner Category
- WarpIntel setup verification
- Next Step
- Configure WarpIntel-only DSNs and the capture feature flag only after scrub rules are reviewed and a non-sensitive sample capture is approved.
- Launch Impact
- Staged for final configuration, link validation, or smoke testing.
#6 / Revenue And Growth
Stripe
- Public State
- Feature-flagged off
- Owner Category
- Feature-gate review
- Next Step
- Create and verify WarpIntel-only support links before enabling the public Stripe flag.
- Launch Impact
- Held behind an explicit public feature flag.
#7 / Intelligence
OpenAI
- Public State
- Feature-flagged off
- Owner Category
- Feature-gate review
- Next Step
- Keep deterministic tools live until production AI spend and key ownership are approved.
- Launch Impact
- Held behind an explicit public feature flag.
Core Platform
Neon Postgres
- Public State
- Live
- Current Detail
- The dedicated database connection is present for runtime queries.
- User Value
- Dedicated database lane for protected queues, reports, and future account records.
- Data Boundary
- Public pages expose readiness counts only; database URLs and rows are excluded.
- Next Step
- Keep future persistence inside the dedicated WarpIntel Neon project.
Core Platform
Public Route Smoke
- Public State
- Live
- Current Detail
- Protected health checks probe key public pages and feeds so broken routes are visible from the ops dashboard.
- User Value
- Production smoke checks for public pages, feeds, and protected boundary routes.
- Data Boundary
- Route, status, and header evidence only; response bodies for protected routes are not read.
- Next Step
- Expand smoke coverage whenever a public or protected production route is added.
Core Platform
warpintel.app
- Public State
- Live
- Current Detail
- Custom domain is live on Vercel-managed HTTPS.
- User Value
- Production HTTPS entry point for public tools and trust pages.
- Data Boundary
- Domain and TLS metadata only; no account, provider, or EVE private data.
- Next Step
- Keep Vercel-managed HTTPS as the active public host.
Core Platform
zKillboard Public Data
- Public State
- Live
- Current Detail
- Bounded public killmail and profile-stat lookups are used with attribution, caching, and human-review boundaries.
- User Value
- Public combat context for profile, system, and risk tools.
- Data Boundary
- Bounded public zKillboard data with attribution; no private character tokens.
- Next Step
- Keep bounded public lookups cached and attributed.
EVE Private Data
EVE SSO
- Public State
- Staged
- Current Detail
- Credentials are configured, but sign-in is hidden by feature flag.
- User Value
- Future optional sign-in for dashboard, corp, SRP, fleet, and permissioned modules.
- Data Boundary
- First sign-in stays publicData only; private scopes are feature-specific and consent-previewed.
- Next Step
- Enable public EVE login only after callback, scope map, and live test gates are ready.
Revenue And Growth
AdSense
- Public State
- Waiting
- Current Detail
- Google verification is required before site review can finish.
- User Value
- Optional public ad placements after account verification and site review.
- Data Boundary
- Publisher and slot readiness only; private EVE data is never shared with ad slots.
- Next Step
- Finish Google verification and keep ad slots hidden until publisher and slot IDs are approved.
Revenue And Growth
Growth Telemetry
- Public State
- Live
- Current Detail
- Vercel Analytics and Speed Insights are rendering for aggregate traffic and performance visibility.
- User Value
- Aggregate public traffic and performance signals for launch decisions.
- Data Boundary
- Aggregate telemetry only; private account data and EVE tokens are excluded.
- Next Step
- Enable only the WarpIntel-approved analytics lanes needed for launch review.
Revenue And Growth
Stripe
- Public State
- Feature-flagged off
- Current Detail
- Kept off until donation links are created inside the WarpIntel Stripe account.
- User Value
- Voluntary support and donation links without feature unlocks or private-data access.
- Data Boundary
- Public link readiness only; payment profile details, webhooks, and secrets are excluded.
- Next Step
- Create and verify WarpIntel-only support links before enabling the public Stripe flag.
Comms
Discord
- Public State
- Waiting
- Current Detail
- Discord human verification is required before bot credentials can be created.
- User Value
- Future Discord command, notification, and role-sync workflows.
- Data Boundary
- Command manifest and endpoint readiness only; bot tokens and guild secrets are excluded.
- Next Step
- Complete Discord app verification, then validate the signed interaction endpoint.
Comms
Resend
- Public State
- Waiting
- Current Detail
- The email provider account is under provider review after our 2026-06-13 reply; choose an approved fallback before sending.
- User Value
- Future transactional email for support, queue, and account notifications.
- Data Boundary
- Provider readiness only; API keys, sender credentials, and mailbox contents are excluded.
- Next Step
- Wait for approved sending provider or fallback before enabling transactional sends.
Intelligence
OpenAI
- Public State
- Feature-flagged off
- Current Detail
- AI feature flag is off; tools use deterministic analysis.
- User Value
- Optional AI enhancement for intel, fit, and loss-review workflows.
- Data Boundary
- Feature readiness only; API keys, raw private inputs, and hidden prompts are excluded.
- Next Step
- Keep deterministic tools live until production AI spend and key ownership are approved.
Monitoring
Sentry Error Monitoring
- Public State
- Staged
- Current Detail
- Sentry SDK instrumentation and scrub rules are installed, but capture remains gated until WarpIntel DSNs and the feature flag are approved.
- User Value
- Gated exception monitoring with scrubbed client, server, and edge instrumentation already staged.
- Data Boundary
- Monitoring readiness only; DSNs, event URLs, stack traces with secrets, and private payloads are excluded.
- Next Step
- Configure WarpIntel-only DSNs and the capture feature flag only after scrub rules are reviewed and a non-sensitive sample capture is approved.
No-Secret Integration Rule
Public integration readiness exposes service status, feature-gate state, public action priorities, public value, and next-step summaries only. It excludes provider credentials, payment profile details, API keys, EVE tokens, private EVE data, account data, raw submissions, private logs, and hidden setup packets.