Verified work. Receipts behind every number.

NextBid — a government-bid data platform

The situation (October 2026): a working data API and MCP server with ~35,000 open government bids, but no AI-assistant presence (0 of 3 neutral searches), no registry listing, drifting public docs, source code living only on production machines, and backups that had never been restore-tested.

What Keystone did

• Launch readiness audit — found API keys written to access logs; logging fixed and old logs sanitized the same day. Documentation drift corrected.
• AI distribution — specified anonymous tool discovery with protected data; published the official MCP Registry listing with domain verification; tested keyed searches end to end from an AI client; built a public integrations repository (docs and examples, no production code).
• Source recovery — code from four PCs and two cloud servers to private repositories; fresh clones verified against manifests; secrets scan clean; per-repository deploy keys.
• Disaster recovery — all eleven production databases restored in isolation with zero errors (largest 15.5 GB, 1 h 45 m); encrypted off-site backups for billing, vault and portal data; database roles and configuration captured nightly; weekly automated restore tests; application start tests; a clean-room recovery rehearsal on an off-site machine.
• Security hardening — master-level storage key replaced by per-machine restricted keys; owner-account keys retired from servers; four-state monitoring (healthy / warning / critical / unknown) with email alerting.

Verified outcomes

Not yet proven — and we say so

AI-referred traffic, trials and paying customers are not yet measured; off-site key custody and the final clean-room run await owner steps; the paid-search pilot is deliberately on hold until tracking is live. We’ll update this page when those numbers exist.