Production-safe lanes available now.
WarpIntel live state
Status
Public tools are live first. Private EVE, Discord, email, ads, paid support, and AI lanes stay gated until the matching provider approval, project credential, and user-consent boundary is ready.
External or approval-bound lanes still held behind flags.
Public or browser-local workflows users can open today.
Data stays in the visitor's browser unless exported.
Auth, account, intake, admin, and cron responses avoid browser caching.
Future private/corp lanes needing stricter review.
Public production checks tracked by health and live smoke.
Manual queue submissions are covered by hashed quota checks.
Browser security headers are exposed and smoke-verified.
Service State
EVE SSO
partialCredentials are configured, but sign-in is hidden by feature flag.
Neon Postgres
readyThe dedicated database connection is present for runtime queries.
OpenAI
offAI feature flag is off; tools use deterministic analysis.
warpintel.app
readyCustom domain is live on Vercel-managed HTTPS.
zKillboard Public Data
readyBounded public killmail and profile-stat lookups are used with attribution, caching, and human-review boundaries.
Public Route Smoke
readyProtected health checks probe key public pages and feeds so broken routes are visible from the ops dashboard.
Stripe
offKept off until donation links are created inside the WarpIntel Stripe account.
Resend
blockedThe email provider account is under provider review after our 2026-06-13 reply; choose an approved fallback before sending.
AdSense
blockedGoogle verification is required before site review can finish.
Discord
blockedDiscord human verification is required before bot credentials can be created.
Growth Telemetry
readyVercel Analytics and Speed Insights are rendering for aggregate traffic and performance visibility.
Sentry Error Monitoring
partialSentry SDK instrumentation and scrub rules are installed, but capture remains gated until WarpIntel DSNs and the feature flag are approved.
Production Checks
Route smoke coverage is mirrored into public health as counts only, so uptime monitors can confirm coverage without touching private account data.
Public pages, tool routes, workflow pages, trust pages, and public feed endpoints.
All 8 route-smoke MVP floors are met.
Public ESI, browser-local, and advisory tool routes covered by production checks.
SRP, access, recruitment, mining, fleet, reports, guides, and support intake pages.
Trust, sources, attribution, privacy, terms, data rights, ads, and referral boundaries.
Health JSON, release, roadmap, integration, source, trust, security, scope, report, tool, local-tool, ads, manifest, sitemap, and robots feeds.
Dashboard, permissions, EVE session, and consent-preview account boundary routes.
Manual queue POST routes are smoke-checked with safe invalid submissions.
Analyzer POST responses are smoke-checked as invalid and valid private no-store JSON.
First-party analytics POST responses are smoke-checked as private no-store JSON.
Public EVE tool POST responses are smoke-checked as invalid and valid private no-store JSON.
PI template and sovereignty overview GET responses are smoke-checked as private no-store JSON.
Discord command manifest and interaction status responses are smoke-checked as private no-store JSON.
Support, project-support, ad-choice, terms, privacy, and ads.txt pages are checked for public-launch monetization boundaries.
Unsigned session, export, delete, disconnect, and logout controls are verified as private responses.
Ops review, launch blockers JSON/Markdown, JSON snapshot, and queue CSV routes are verified as private status/header checks.
External-service setup packet routes are verified as private status/header checks.
EVE SSO dry run, EVE SSO activation rehearsal, EVE token revocation drill, external feature activation dry run, Discord command registration, Discord command dry run, Discord activation rehearsal, OpenAI dry run, OpenAI activation rehearsal, Growth dry run, Vercel/GitHub dry run, backup recovery dry run, reports webhook dry run, transactional email dry run, transactional email activation rehearsal, Stripe support dry run, Stripe support activation rehearsal, AdSense config dry run, AdSense activation rehearsal, Sentry config dry run, and Sentry activation rehearsal are verified as admin-only private setup actions.
Queue, rules, health, and fleet action routes are verified as admin-only private responses.
Ops login page plus failed-login and logout redirects are verified as private responses.
EVE SSO callback state-failure redirects are verified as private responses.
6/6 human-readable and JSON EVE consent-preview routes.
Public status shows route-smoke coverage counts only; protected and intake checks store status, header, and redirect evidence only and never read response bodies, cookies, EVE tokens, provider secrets, pasted form text, or private account data.
Intake Guard
Public manual queue submissions have a shared abuse guard before they write to the review queues.
Support, access, SRP, recruitment, buyback, and mining submission routes share the guard.
Tunable through PUBLIC_INTAKE_RATE_LIMIT and PUBLIC_INTAKE_RATE_LIMIT_WINDOW_SECONDS.
Requester identity is salted and hashed before any quota event is stored.
Exceeded requests are recorded as rate_limit audit events for protected ops review.
Manual intake quota events store the route, cost, timestamp, and salted requester hash only; they do not store raw IP addresses, raw user-agent strings, form messages, EVE tokens, provider secrets, or pasted tool inputs.
Security Baseline
Browser security headers are checked in production smoke and mirrored into public health as counts only.
Production responses require Strict-Transport-Security with includeSubDomains.
X-Frame-Options and CSP frame-ancestors keep WarpIntel out of hostile frames.
Content sniffing, referrer, camera, microphone, geolocation, payment, USB, and topics are restricted.
Launch CSP is visible and smoke-verified without blocking approved public integrations yet.
The public security baseline reports header categories and policy mode only; it does not expose cookies, sessions, admin paths, provider secrets, EVE tokens, or visitor identifiers.
Launch Action Queue
The top gated launch actions stay visible here as sanitized priorities while the full queue remains in the launch readiness manifest.
3 waiting; 5 staged; 0 planned.
Discord Bot And Role Sync: Complete Discord human verification on Zeus, then add the app public key, client ID, bot token, and guild ID.
Queue items stay grouped by public owner category rather than internal account names.
The launch readiness manifest mirrors sanitized queue counts for public monitors.
Complete Discord human verification on Zeus, then add the app public key, client ID, bot token, and guild ID.
Comms / Project owner review / Waiting on provider review, account verification, or owner action.Complete Google verification on Zeus, then finish AdSense submission and store the publisher/client ID.
Ads / Project owner review / Waiting on provider review, account verification, or owner action.Use the protected email setup packet, then wait for Resend approval or choose another approved sender before enabling transactional mail.
Email / Provider review / Waiting on provider review, account verification, or owner action.Use the protected Growth packet when setting up Vercel Analytics, Speed Insights, Search Console, or Bing Webmaster Tools.
Growth / WarpIntel build team / Staged for final verification before public activation.Public status launch action queue exposes only sanitized priorities, public state, public owner category, area, next-step summaries, launch-impact text, and aggregate counts; it does not expose provider credentials, API keys, passwords, payment profile details, EVE tokens, private EVE data, raw submissions, setup packets, internal account names, or separate-project account details.
Integration Action Queue
The top gated integration actions stay visible here as sanitized priorities while the full provider queue remains in the integrations manifest.
3 waiting; 2 staged; 2 feature-gated; 0 planned.
AdSense: Finish Google verification and keep ad slots hidden until publisher and slot IDs are approved.
EVE, revenue, and communications integration lanes still needing gated follow-up.
The integrations manifest mirrors sanitized queue counts for public monitors.
Finish Google verification and keep ad slots hidden until publisher and slot IDs are approved.
Revenue And Growth / Provider or account review / Cannot activate public provider behavior until verification or approval clears.Complete Discord app verification, then validate the signed interaction endpoint.
Comms / Provider or account review / Cannot activate public provider behavior until verification or approval clears.Wait for approved sending provider or fallback before enabling transactional sends.
Comms / Provider or account review / Cannot activate public provider behavior until verification or approval clears.Enable public EVE login only after callback, scope map, and live test gates are ready.
EVE Private Data / WarpIntel setup verification / Staged for final configuration, link validation, or smoke testing.Public status integration action queue exposes only sanitized priorities, public state, public owner category, provider category, next-step summaries, launch-impact text, public links, and aggregate counts; it does not expose provider credentials, payment profile details, API keys, EVE tokens, private EVE data, account data, raw submissions, private logs, setup packets, internal account names, or separate-project account details.
Open Health JSONOpen Release JSONOpen Release Readiness JSONOpen Roadmap JSONOpen Integrations JSONOpen Launch JSONOpen Launch QueueOpen Integration QueueOpen Source JSONOpen Trust JSONOpen Security JSONOpen Legal ReadinessOpen Legal Readiness JSONOpen Report ManifestOpen Tool Directory JSONOpen Local Tool Readiness JSONOpen Release NotesOpen Release Readiness
AI Readiness
AI assistance is staged with deterministic fallback, protected setup review, and no-provider-call dry runs while provider keys, prompts, spend records, and private EVE data stay out of public surfaces.
Intel Desk, Fit Coach, and Loss Reviewer can use deterministic analysis now and AI later.
Setup packet, dry-run, and activation rehearsal stay behind protected admin routes.
Owner review can package first-tool AI activation evidence without provider calls or token spend.
Public tools keep returning deterministic local analysis if AI is disabled or unavailable.
Readiness checks do not call OpenAI, submit prompts, or spend tokens.
Public AI readiness exposes aggregate first-tool counts, feature-gate booleans, activation criteria, activation-rehearsal counts, protected-check booleans, deterministic fallback status, and no-provider-call dry-run status only; it does not expose provider keys, model environment values, billing details, raw prompts, raw pasted analyzer inputs, EVE tokens, private account data, or token-spend records.
Backup Readiness
Recovery posture is public as aggregate counts while database URLs, cron secrets, migration tags, SQL dumps, provider-console artifacts, and restore evidence stay protected.
Recovery prerequisites are tracked as public-safe counts while restore artifacts stay protected.
Migration count is visible without exposing migration tags, SQL bodies, or database connection values.
Setup packet, recovery dry-run, and restore-drill rehearsal coverage stay behind protected admin routes.
The app is ready for an owner-reviewed drill; the public page does not claim a real restore is verified.
A real restore drill must prove release fingerprint, route smoke, migration ledger, ops snapshot, and tracker evidence before it is marked verified.
The restore drill has a secret-free handoff covering baseline, provider boundary, isolated restore, migration reconcile, proof review, and tracker record.
Deployment, data-restore, and environment-boundary rollback decisions are documented without exposing provider artifacts.
Public backup readiness exposes aggregate recovery counts, activation criteria, migration count, protected-check booleans, proof-target counts, safe-export counts, restore-drill acceptance-criteria counts, owner-handoff counts, rollback decision counts, restore-drill status, and no-provider-mutation dry-run status only; it does not expose database connection values, cron secret values, migration tags, Neon passwords, SQL dumps, Vercel rollback targets, provider-console backup artifacts, token ciphertext, raw IP addresses, raw user-agent strings, EVE tokens, private account data, or raw pasted analyzer inputs.
Growth Readiness
Growth setup is staged with explicit telemetry flags, search-verification gates, protected dry runs, and no-provider-call boundaries while analytics IDs, verification token values, and provider accounts stay out of public surfaces.
Growth telemetry and search verification prerequisites are tracked as aggregate counts.
Analytics and Speed Insights stay behind explicit public feature flags.
Google and Bing verification values are never echoed from public readiness surfaces.
Telemetry and search submission cannot be marked launch-ready until every no-secret criterion passes.
Readiness checks do not call analytics, Search Console, Webmaster Tools, or provider accounts.
Public growth readiness exposes aggregate telemetry counts, search-verification counts, activation-criteria counts, owner-handoff counts, rollback decision counts, installed-component counts, protected-check booleans, and no-provider-call dry-run status only; it does not expose analytics IDs, verification token values, Google or Bing account details, provider cookies, Search Console screenshots, raw pageview data, workflow-click payloads, EVE tokens, private account data, or raw pasted analyzer inputs.
SEO Readiness
Search discovery is public and count-only: sitemap, robots, app manifest, guide metadata, tool metadata, and search-verification gates are monitored without exposing provider tokens or private EVE data.
Public discovery routes are listed without private or protected URLs.
Protected account, ops, dashboard, API, and preview paths stay blocked from crawlers.
Guide detail pages expose reviewed titles, descriptions, canonical links, and Open Graph data.
Public tool pages have static discovery metadata while analyzer inputs remain unstored.
Public SEO readiness health exposes aggregate sitemap, robots, web-app-manifest, guide, guide-detail metadata, tool-detail metadata, and search-verification gate counts only; it does not expose verification token values, analytics IDs, Search Console accounts, provider cookies, EVE tokens, private EVE data, admin exports, raw logs, or raw pasted analyzer inputs.
Capability Readiness
Capability readiness rolls up public tools, browser-local workflows, protected review queues, EVE consent gates, and provider-gated lanes without exposing private EVE data or setup details.
No-login tools and public EVE data surfaces that users can open today.
Planning workflows that keep working state in the visitor browser unless exported.
Manual intake and review lanes that stay behind protected reviewer surfaces.
EVE SSO and external-provider features remain staged until approval, credentials, and consent are ready.
Public capability readiness exposes aggregate capability counts, route-link counts, consent-preview counts, provider-gate counts, link counts, and safety-boundary counts only; it does not expose provider credentials, EVE tokens, private EVE data, account data, raw submissions, private logs, hidden setup packets, internal account names, or separate-project account details.
EVE Login Gate
EVE sign-in stays hidden until the callback, first-login scope, and live test gate are all ready.
EVE sign-in is feature-flagged off until the production callback is confirmed and a test sign-in succeeds.
Expected callback: https://warpintel.app/api/auth/eve/callback
First sign-in must remain limited to public identity before private modules ask for more.
High-trust and write/action scopes stay feature-specific, consent-previewed, and human-reviewed.
9/10 permission group(s) are fully allowed; 1 partial and 0 missing.
8 preview-only feature path(s) staged before OAuth; 1 high-trust action lane(s).
Public EVE gate health exposes status booleans, safe counts, permission-group coverage counts, preview-only feature consent metadata, activation criteria, owner-handoff counts, owner proof-target counts, rollback decision counts, the expected callback, and runtime login guard state only; it never exposes client IDs, client secrets, EVE tokens, account data, or private EVE data.
Permission Catalog
Scope catalog readiness stays public and count-only: it shows reviewed groups, known scopes, consent-preview coverage, and OAuth boundaries without exposing credentials or private EVE data.
1 available now; 8 future gated group(s).
63 known scope(s); 0 unknown.
8 feature route(s) have dry preview coverage.
8 write/action scope(s) stay feature-gated.
Catalog and consent-preview routes do not start OAuth or contact CCP.
Manifest links and safety boundaries stay public and count-only.
Public EVE permission catalog readiness health exposes aggregate scope counts, group counts, consent-preview counts, feature consent route counts, link counts, and safety-boundary counts only; it does not start OAuth, contact CCP, expose EVE tokens, client secrets, private EVE data, account data, raw submissions, internal account names, or separate-project account details.
Data Rights Readiness
Browser-local data controls are public, signed-in account export/delete/disconnect routes stay private, and readiness is exposed as counts only.
Public tools keep local records in the visitor browser until exported or cleared.
Signed-in exports are private no-store JSON and do not include token values.
Account delete, EVE disconnect, and logout paths are smoke-checked as private responses.
Public readiness exposes counts, links, and safety booleans only.
Public data-rights readiness exposes public route counts, account-control route counts, browser-local surface counts, protected smoke counts, and safety booleans only; it does not expose account exports, EVE OAuth token values, token ciphertext, provider secrets, private EVE data, raw pasted inputs, raw visitor identifiers, raw browser agent strings, payment profile details, raw support messages, or manual review queue notes.
Reports Readiness
Local reports stay browser-local by default, public export manifests describe safe formats, and account report saves remain private no-store flows after EVE sign-in.
Report save, copy, download, import, and export stay in the visitor browser by default.
Markdown bundle, JSON backup, and account-report JSON boundaries are public-safe.
Account saves require EVE sign-in and private no-store responses.
Outbound delivery waits for signing, replay protection, rate limits, and abuse review.
Public reports readiness exposes aggregate report-format counts, tool counts, endpoint counts, public link counts, workflow-stage counts, webhook safety flags, and exclusion counts only; it does not expose report bodies, raw pasted analyzer inputs, account reports, account exports, EVE OAuth token values, token ciphertext, provider credentials, private EVE data, raw visitor identifiers, raw browser agent strings, webhook signing secrets, or separate-project account details.
Support Readiness
Support requests, voluntary support, Stripe support-link exposure, and email receipts stay public-safe: provider lanes remain gated until review, and support queue details stay protected.
Support request, voluntary support, and support readiness pages are public.
Support submissions enter a protected queue for human review.
Stripe, email, and revenue providers stay dry-run or public-gated.
Voluntary support does not unlock gameplay, EVE data, or dashboard access.
Public support readiness exposes support surface counts, support request route counts, protected review counts, provider-gate counts, workflow-stage counts, and no-live-provider safety booleans only; it does not expose raw support messages, raw support subjects, contact details, email addresses, Discord handles, in-game names, page URLs, admin review notes, reply draft bodies, support queue statuses, rate-limit hashes, browser identifiers, EVE session ids, EVE tokens, Stripe customer records, payment profile details, provider secrets, email message ids, paid unlocks, or account decisions.
Domain Contact Readiness
WarpIntel domain, HTTPS contact, support mailbox, security policy, and provider-boundary disclosures stay public-safe while registrar, DNS, TLS, mailbox, and provider account details remain excluded.
The public app canonical domain is documented for checks and disclosure pages.
Security policy and security.txt point to the public support contact path.
support@warpintel.app is the public contact lane for support and security intake.
Registrar, DNS, TLS, mailbox, payment, ad, and API provider details stay out of public output.
Public domain readiness exposes only the production domain, public support contact, route counts, policy/contact route lists, provider-boundary counts, and no-secret safety booleans; it does not expose registrar account details, DNS zone records, TLS certificate private keys, mailbox credentials, provider console account ids, payment account details, ad account details, email provider API keys, database URLs, OAuth client secrets, EVE access tokens, private EVE data, admin notes, raw support messages, or separate-project account details.
Market Readiness
Market Command and Appraisal Desk stay public and manual, browser-local watchlists remain local, and private market/asset/wallet context waits for feature-specific consent.
Public market comparison works without EVE sign-in or private orders.
Item-list pricing uses public market data and user-entered text only.
Saved market reminders stay in the browser and never become trade instructions.
Private assets, orders, wallets, contracts, and jobs wait for feature consent.
Public market readiness exposes public route counts, public API route counts, workflow-stage counts, consent-preview links, and safety booleans only; it does not expose private market orders, wallet journals, asset locations, contract records, market order ownership, industry jobs, character contact details, raw saved watchlist entries, EVE tokens, provider secrets, private EVE data, or automated trade actions.
PI Readiness
PI planning is public and advisory, market estimates use public data, and future colony review waits for feature-specific EVE consent.
13 reviewed PI templates can be planned without EVE sign-in.
Optional price checks use public ESI market estimates and stay advisory.
Private colony review waits for feature-specific consent and clear wording.
Colony routing, client actions, hauling, and tax decisions stay manual.
Public PI readiness exposes PI template counts, public route counts, public API route counts, protected setup route counts, workflow-stage counts, consent-preview links, and safety booleans only; it does not expose private colony layouts, planet pin positions, extractor routes, storage levels, customs office ownership notes, private assets, wallet journals, industry job history, EVE tokens, provider secrets, private EVE data, colony read automation, or colony write automation.
Navigation Readiness
Systems, routes, maps, sovereignty, structures, and wormhole views stay public-data first while private live-intel context waits for feature-specific consent.
Systems, routes, map, sovereignty, structures, and wormholes stay public-data ready.
System risk, route scout, sovereignty, and readiness endpoints are smoke-covered.
Location, online state, ship type, and private killmail context wait for consent.
Travel decisions, fleet movement, scouting, and in-game actions stay manual.
Public navigation readiness exposes public page counts, public route counts, public API route counts, workflow-stage counts, consent-preview links, and safety booleans only; it does not expose pilot location, online state, ship type, private route history, private bookmarks, private fleet membership, fleet participation ledgers, private killmails, structure access lists, EVE tokens, provider secrets, private EVE data, location read automation, or fleet action automation.
Access Readiness
Access requests, first-login scope, feature consent previews, and grant boundaries are public-safe while raw request details, reviewer notes, role sync, and private EVE data stay protected.
Access requests can be submitted publicly and enter protected manual review.
Basic sign-in stays limited to public identity; private scopes are feature-specific.
High-trust and write-action permissions remain previewed before any provider redirect starts.
Approvals, expiries, Discord role sync, and grants are never automated from public request data.
Public access readiness exposes access surface counts, public route counts, protected review route counts, consent-route counts, workflow-stage counts, feature-consent counts, and no-secret safety booleans only; it does not expose raw access request rows, character names, corporation or alliance labels from submitted rows, raw access reasons, contact details, Discord handles, evidence URLs, sponsor references, admin reviewer notes, access grant state, rate-limit hashes, browser identifiers, EVE session ids, EVE tokens, private EVE data, role-sync payloads, provider secrets, automated approvals, or access grants.
Operations Intake Readiness
Access, recruiting, and support intake are public and guarded, while request rows, reviewer notes, and account decisions stay protected and human-reviewed.
Access, recruiting, and support intake pages are public.
Manual submissions use shared abuse protection before queue writes.
Status changes and reviewer notes stay behind admin access.
Emails, approvals, denials, access grants, and account decisions stay human-approved.
Public intake readiness exposes public route counts, submission route counts, protected review route counts, workflow-stage counts, and safety booleans only; it does not expose raw access requests, recruitment applications, support messages, applicant names, contact details, vouch notes, admin review notes, audit event metadata, rate-limit hashes, EVE session ids, EVE tokens, provider secrets, private EVE data, notification sends, or account decisions.
SRP Readiness
SRP intake is public, review stays protected, and future proof context waits for feature-specific EVE consent.
Loss requests can be submitted without private EVE data.
Queue review and decision notes stay behind admin access.
Reserve exports use aggregate guidance and exclude raw queue details.
Private SRP proof context waits for feature-specific EVE consent.
Public SRP readiness exposes public route counts, protected route counts, workflow-stage counts, consent-preview links, and safety booleans only; it does not expose pilot names, killmail URLs, raw SRP queue notes, wallet balances, contract data, EVE tokens, provider secrets, private EVE data, or payout actions.
Fleet Readiness
Fleet scheduling is public and manual, publishing stays protected, and future fleet context/action scopes wait for feature-specific consent.
Public ops can be reviewed without EVE sign-in or private fleet reads.
Fleet/timer publishing remains admin-only and smoke-checked as private.
Participation and SRP proof context waits for feature-specific consent.
Fleet write/client actions require high-trust consent and a human confirmation flow.
Public fleet readiness exposes public route counts, protected publish route counts, workflow-stage counts, consent-preview links, and safety booleans only; it does not expose private fleet membership, fleet participation ledgers, FAT links, pilot location, online state, ship type, private killmails, fleet invitation tokens, EVE tokens, provider secrets, private EVE data, or fleet write actions.
Mining Readiness
Mining intake is public and manual, queue review stays protected, and future mining/wallet/contract reconciliation waits for feature-specific consent.
Ore, loot, proof, and split notes can be submitted for manual review.
Mining queue decisions and payout notes stay behind admin access.
Private mining history, assets, contracts, and wallet context wait for consent.
ISK movement, contracts, and corp cuts are never automated by the public lane.
Public mining readiness exposes public route counts, intake route counts, protected review route counts, workflow-stage counts, consent-preview links, and safety booleans only; it does not expose raw ore or loot lines, proof URLs, payout character notes, wallet journals, contract records, asset locations, corporation mining ledgers, member mining history, EVE tokens, provider secrets, private EVE data, ISK movement, or contract automation.
Buyback Readiness
Buyback calculator and request intake are public and manual, review stays protected, and future asset/contract/wallet reconciliation waits for feature-specific consent.
Public buyback estimates work without EVE sign-in or stored account data.
Buyback requests enter a protected review queue through the shared intake guard.
Private assets, contracts, wallets, and market context wait for feature consent.
Contracts, accepted locations, hauling decisions, and ISK movement are never automated by the public lane.
Public buyback readiness exposes public route counts, intake route counts, quote route counts, protected review route counts, workflow-stage counts, consent-preview links, and safety booleans only; it does not expose raw item list rows, proof URLs, character contact details, requested locations, contract character notes, raw buyback queue notes, wallet journals, contract records, asset locations, corporation buyback ledgers, EVE tokens, provider secrets, private EVE data, ISK movement, or contract automation.
Tool Boundaries
LocalBrowser local
Dashboard Command StateReads reports, fits, watchlists, market watches, plans, skills, learning, and wormhole boards from this browser.
No local notes, fits, reports, or planning state are sent to the server.LocalBrowser local
Local Report LibraryCopies, downloads, filters, imports, exports, and deletes browser-local WarpIntel reports.
Stores generated summaries locally; raw pasted inputs are not stored server-side.LocalBrowser local
Fit LabParses pasted fits, saves local fit records, compares two fits, and routes into Fit Coach review.
No private skills, implants, hangars, or EVE fitting writes are used.LocalBrowser local
Character AuditMaps manual notes for identity, skills, clones, assets, wallet, contracts, industry, PI, and fleet/SRP context.
Manual review shell only; no private EVE character data is pulled yet.LocalBrowser local
Corp StatsParses pasted roster notes into registration, main/alt, activity, role coverage, follow-ups, and exports.
Roster snapshots stay in the browser unless manually exported.LocalBrowser local
Corp AuditReviews manual director notes for access, roles, wallets, assets, contracts, structures, industry, markets, and security.
No corporation wallets, assets, contracts, or member data are read from EVE yet.LocalBrowser local
Structure WatchTracks pasted fuel, timers, POCOs, starbases, bridges, facilities, moon pulls, and director actions.
Manual notes only; no corp structures or fuel data are fetched.LocalBrowser local
Skill PlannerBuilds manual doctrine readiness plans for tackle, DPS, logistics, wormholes, industry, and PI.
Manual level selectors stay local; no private skill queue is read yet.LocalBrowser local
Public WatchlistsStores local pilots, corps, alliances, systems, items, fits, fleet notes, tags, priorities, and backups.
Watchlists remain local and portable through manual export/import.LocalBrowser local
New Player Mission ControlTracks beginner mission paths, practical habits, safety warnings, and links into live public tools.
Learning progress is local and does not create server-side profile data.LocalBrowser local
PvE Site HelperGuides manual PvE prep with danger signals, fit checks, route checks, and copyable briefings.
No client automation, no site detection, and no private character reads.LocalBrowser local
Manual Wormhole OpsBuilds local chain maps, system notes, signatures, mass/lifetime states, scout briefs, and backups.
Manual chain data stays local unless exported or later synced by choice.Public dataPublic ESI
Market CommandUses public market orders for hub comparison and keeps item watchlists in browser storage.
Public ESI prices plus local watchlists; no trading action or order writes.Public dataPublic ESI
Public ProfilesResolves exact public characters, corporations, and alliances with ESI identity facts, image-server portraits/logos, alliance corporation samples, and bounded zKillboard stats.
Public ESI and zKillboard advisory data only; no private character, corporation, wallet, role, or activity data is read.Public dataPublic ESI
Intel MapDraws a visual route-risk map from public ESI route, system security, kill, pod, jump, and watchpoint data.
Public advisory map only; no client destination setting, location tracking, or private character data.Public dataPublic ESI
Industry LabUses reviewed SDE blueprint data, user-entered materials, public prices, and local blueprint workspace backups.
Manual planning only; it does not start jobs, move items, or read private hangars.Public dataPublic ESI
PI PlannerPlans reviewed P0-P3 production chains with raw extraction estimates, user inputs, tax reserve, and public price estimates.
Public calculator only; no colony reads, edits, or EVE client actions.