Go to /signup, enter the fully qualified domain name (FQDN) of the site you want to protect, and complete payment via Stripe ($49/month).
We resolve your domain to its current IP address before you make any DNS changes. This becomes the "origin IP" that Yod proxies traffic to.
After payment, we automatically provision a dedicated VM for your instance. You'll receive an email with your instance IP address, admin password, and DNS instructions.
You can also watch provisioning progress on your dashboard.
Create two DNS A records pointing to your Yod instance IP:
example.com → <your-instance-ip>
yod.example.com → <your-instance-ip>
The first record routes your site's traffic through Yod. The second gives you access to the Yod console.
DNS propagation typically takes 5-30 minutes. Your dashboard auto-checks and shows a green indicator when ready. Caddy automatically provisions Let's Encrypt TLS certificates for both domains.
Once DNS is verified, open your console at https://yod.yourdomain.com and log in with your admin password.
Enter your application's session cookie name(s) — for example PHPSESSID, connect.sid, or _session_id. This enables session-level attack detection (correlating multiple requests from the same attacker). Without it, Yod still detects per-request attacks.
For AI-powered attack analysis, configure an Anthropic API key or Ollama URL. Without an AI provider, Yod still detects and redirects — just without AI analysis summaries.
For maximum protection, configure your origin server's firewall to only accept HTTP/HTTPS traffic from your Yod instance IP. This prevents attackers from bypassing Yod by connecting directly to your origin.
# Example: UFW on Ubuntu
ufw allow from <yod-instance-ip> to any port 443
ufw allow from <yod-instance-ip> to any port 80
If the Yod router ever becomes unresponsive, Caddy automatically fails over to proxying traffic directly to your origin server. Your site stays up — just temporarily unprotected. When Yod recovers, traffic routes back through it automatically. You'll see failover alerts on your dashboard and receive an email notification.
Your site stays online. Caddy health-checks the Yod router every 5 seconds and automatically fails over to proxying directly to your origin. When Yod recovers, it switches back.
No. Yod works as a transparent reverse proxy. No SDKs, no code changes, no agents to install.
A dedicated VM running the full Yod stack, automatic TLS, real-time detection console, automatic updates with rollback, and failover protection. AI analysis is BYOAI — you provide your own Anthropic API key or Ollama URL.
Keeping AI costs out of the base price lets us offer Yod at $49/month with 88% gross margin. You control your AI spend and can choose between cloud (Anthropic) or self-hosted (Ollama) models.
No. Every customer gets a completely isolated VM with its own database. No shared infrastructure, no shared state. Your traffic and detection data never leaves your VM.
Contact us. We can upgrade your VM to a higher tier to handle more traffic.
Yod has an update agent that checks for new versions every 15 minutes. Updates roll out via canary strategy (10% of instances first) with automatic rollback if health checks fail. Zero maintenance on your end.
Yes. Go to Dashboard > Billing > Manage Subscription to cancel. Your instance will be destroyed after the current billing period.
The cookie your application uses to track logged-in users. Common examples: PHPSESSID (PHP), connect.sid (Express.js), _session_id (Rails), JSESSIONID (Java). Check your browser's developer tools (Application > Cookies) to find yours.
Not for the MVP tier. Yod is designed for high availability with automatic failover, but we don't offer formal SLA guarantees yet.