Checking...

Where Napoleon Guards Your API Keys

Your secrets are encrypted server-side. Your frontend never sees the real keys.

-
Secrets
0
Routes
The Hutch — Where Napoleon Guards Your API Keys

Now what?

1. Add your first secret

Name it after the service — STRIPE_KEY, OPENAI_KEY. Your app references the name, never the value.

Open dashboard →

2. Call The Hutch from your app

Replace your direct API calls with fetch("/api/your-route"). The Hutch injects the secret and forwards it.

Read the docs →

3. Set up webhook verification

Point Stripe or GitHub at your Hutch URL. The Hutch verifies the signature — your app just reads the clean payload.

Webhook guide →

Want a deeper explanation?

Copy a prompt and paste it into your preferred AI assistant. It'll explain exactly how The Hutch works and answer your questions.


Ready for The Farm?

$29/month

The Hutch secures your secrets. The Farm gives Napoleon the tools to actually use them — running agents, executing pipelines, managing containers, and shipping work while you sleep.

Napoleon runs your workflows

Push a branch, Napoleon runs tests, opens a PR, and deploys — while you're away from your machine.

Docker containers, managed

Run any container in The Pen — isolated, audited, accessible from anywhere, with secrets from your Hutch.

The Mud — full audit trail

Every action logged. Every secret access recorded. Napoleon never acts without a receipt.

Scheduled tasks + pipelines

Health checks, cron jobs, multi-step pipelines. The Farm runs while you're living your life.


This is your Hutch's default landing page. Your SPA connects via /api/* endpoints and won't be affected. To disable this page, set HUTCH_LANDING=false in your container environment.