Database
Database Readiness
WarpIntel uses a protected Neon and Drizzle storage lane for accounts, EVE identity metadata, manual intake, rate limits, audit events, and future account reports. This page shows aggregate readiness only, without connection strings, SQL bodies, row contents, token ciphertext, account exports, or private EVE data.
Production storage is designed around a dedicated WarpIntel Neon Postgres project.
Account, EVE identity, intake, traffic, rate-limit, audit, and settings tables are mapped.
Drizzle migration count is tracked without exposing migration names or SQL bodies.
Connection values, row data, and restore actions stay outside public output.
Support, SRP, access, recruitment, buyback, and mining queues are mapped to protected persistence.
Analyzer and manual-intake policy coverage is staged with safe fallback behavior.
Account-save capable tools remain sign-in gated while local exports stay available.
Storage activation is documented through public-safe criteria and protected owner review.
Account And EVE Identity
Signed-in account, character, token metadata, membership, and saved-report storage stay protected.
Public Traffic And Rate Limits
Public analytics, workflow clicks, tool runs, and rate-limit events use hashed or aggregate metadata only.
Manual Intake Queues
Public forms can collect requests for protected human review without exposing queue rows publicly.
Operations And Settings
Ops, service health, audit, and app setting records remain admin-only and no-store.
Browser-Local First
Public tools can save local reports in the visitor browser before account storage is enabled.
Manual Intake Persistence
Support, SRP, access, recruitment, buyback, and mining forms require protected database writes.
Account Report Storage
Signed-in account reports require EVE SSO, private no-store responses, and protected account controls.
Rate Limit And Abuse Guard
Analyzer and manual-intake abuse controls use hashed identity records when the database is available.
Audit And Review
Admin decisions, service checks, and audit events stay behind protected routes and sanitized exports.
Backup And Recovery
Neon restore drills stay owner-reviewed and separated from public readiness checks.
Public Tool Analyzer
Limit 30; evidence is stored as aggregate policy status while raw visitor identity stays excluded. Use local deterministic analysis when database-backed enforcement is unavailable.
Manual Intake Routes
Limit 8; evidence is stored as aggregate policy status while raw visitor identity stays excluded. Keep request submission guarded and fail closed when protected persistence is unavailable.
Schema surface documented
Public manifest exposes table-group and enum counts without row contents or SQL bodies.
Migration ledger counted
Drizzle migration count is available for readiness without publishing migration names.
Manual intake routes covered
Six public intake routes are mapped to protected persistence and rate-limit policy.
Rate-limit fallback ready
Public tools fall back safely when database-backed rate limiting is unavailable.
Account report boundary ready
Account reports require sign-in and private responses while browser-local exports remain available.
Backup readiness linked
Database recovery evidence links to backup readiness without exposing provider artifacts.
Secret and row exclusion
Connection strings, SQL dumps, row data, token ciphertext, and private account records are excluded.
No-Secret Database Rule
Public database readiness exposes aggregate schema counts, table-group labels, migration counts, workflow-stage counts, rate-limit policy counts, account-report coverage counts, backup-readiness counts, and no-secret boundary booleans only; it does not expose connection strings, database passwords, SQL bodies, migration names, row contents, token ciphertext, private EVE data, account exports, raw submissions, raw logs, provider-console artifacts, or separate-project account details.