Other work
Everything else we're building.
Leviathan Platform is the one product we're currently offering as a paid pilot. Everything on this page is other in-progress work — some live, some prototype-ready, none of it part of the Leviathan Platform pricing or pilot on the main page.
Consumer software
WatchYoDog
A dog-walking companion with a privacy-first architecture — no account, no telemetry, no IP logging, no dark patterns. There are two builds: a web app you can use right now, and a larger Android app still in development. They are not the same, so they're listed separately.
- GPS walk tracking — live route, distance, pace, and a history of every walk
- Walk stats: totals, longest walk, and consecutive-day streaks
- Hazard and lost-pet feed with an interactive map you can drop pins on
- Community forum with categories, upvotes and contribution points
- Walker → Pack Leader → Alpha tiers earned through activity
- 17 breed avatars, or upload your own photo
- Works offline; installs in one tap; updates instantly
Honest status: hazard and lost-pet alerts are shared for real — backed by a real database, visible to everyone using the app, not seeded sample content. Your walks and forum posts still live only on your own device; the shared alert feed was the first piece we networked, not the last.
- On-device ML avatar processing pipeline
- Community Ad Council with voting and report-driven demotion
- Async card game with play-money treat chips — no real money, no purchases
- Offline-safe score sync and local leaderboards
In progress
Beyond the current release.
Other repositories in various states — none of these are part of what's being sold today.
An independent SHA-256 hash-chained persistence substrate that mirrors platform events in a separately-versioned codebase. Cross-language parity with the main platform is enforced as a CI-gated test.
A deterministic, fail-closed PII scrubber for staging databases. HMAC-SHA256 swaps real emails/keys/UUIDs for mathematically-linked honeytoken values — relational integrity survives masking, and a stolen dump becomes a tripwire.
A prompt-injection detector and a Python egress firewall for AI agents/automation you build yourself. Pure standard library, zero pip dependencies, works as an importable library or a standalone CLI.
Honeytoken traps for real infrastructure — AWS/GCP metadata SSRF, a kubeconfig, an SSH key, a poisoned Postman collection, RAG honeydocuments, Ghost-Schema, an LLM tarpit, a decoy MCP server, npm/PyPI registry traps, and more. 362 tests, 20 traps, run standalone or as one combined service.
The SSH key trap from Decoy Kit, given away in full — real, MIT-licensed, no signup. One module extracted into its own public package; the other seven stay in the paid kit.
Linux forensic capture for Leviathan Defense: on a honeytoken trip, freezes the whole process tree, captures memory and resolved sockets, Ed25519-signs the bundle. Verified against a real Linux process tree (WSL2, kernel 6.6) — a real child process frozen and confirmed stopped, a real listening socket resolved by port and state, real captured memory bytes with real SHA-256 hashes, a tampered bundle correctly failing signature verification. 22/22 real checks passing. Needs root for another user's process state — disclosed, not hidden. Windows has no /proc or SIGSTOP, so this is Linux-only by design, not an oversight.
A platform for creators and inventors selling and producing while a patent or copyright filing is still pending: a real Ed25519-signed proof-of-creation record (same signing pattern as Bait-Mask's licenses), plus print-on-demand merch where the factory takes its production fee and the rest goes to the creator. 3% of profit, only once there is any — no equity, no cut when a sale doesn't net anything. No telemetry. Very early: the signing library is built and tested (18/18), the marketplace and live proof-of-creation endpoint aren't yet.
A thin canary seam for a separate payment-gateway codebase. Canary keys minted in the gateway's own format. Detection only — gateway source untouched.
A trust-minimized Bitcoin bridge to a ZK-rollup L2 — an executable specification, not a whitepaper: a real withdrawal contract, an off-chain attestor daemon that checks claimed deposits against live Bitcoin data and signs a 2-of-3 federated attestation, and a relay that batches and submits it on-chain. 180/180 tests passing. A self-audit found and fixed 3 real bugs before this was shown to anyone.
A v1 payment gateway foundation for Norway (Vipps/NOK) — ledger and reconciliation, idempotency keys, merchant and API-key management, a documented zero-trust roadmap. CI is green in a real hosted environment and the Docker image builds and runs for real. Its own go/no-go doc calls this NO-GO as of this writing — not a code defect, but a blocked Vipps business-portal identity check (a BankID re-verification issue) outside what this codebase can resolve on its own. Zero testing against real Vipps infrastructure until that clears.
A self-hosted, file-backed kill switch and webhook broadcast for stopping agent tooling org-wide — a human trips it, every wired guard denies the next call, Slack/Teams gets a real message automatically. No Northstar infrastructure in the path, ever. Wired into MCP Gateway, Agent Guardrails, and Probe Kit (denies the action) and Decoy Kit (mutes alert noise only — a trap going quiet would itself tip off a real attacker). 59 tests plus real cross-process interop tests against all four.
A self-audit of your own infrastructure: point it at a domain you own and it checks it the way an outsider would, in five waves (DNS and email hygiene → what's running → configuration: TLS, headers, cookies → exposed files and services → deeper checks), then records every finding in the platform's tamper-evident evidence log. Because it only ever runs against your own systems, it reminds rather than blocks: a banner asks you to confirm the domain is yours, and hardened admins can skip it in scripted runs. Four scripts (an LLM security probe and three others) held back as a premium tier, not bundled in. Packaged as a standalone distributable; its first packaging test run surfaced 8 real failing stages from a broken internal path — fixed same day, five verification runs since, all 10/10 stages passing.
An early-stage component, not yet ready for external evaluation.