135,000 AI ASSISTANTS EXPOSED TO THE INTERNET
HARDCODED API KEYS FOUND IN PUBLIC REPOS
NO AUTHENTICATION REQUIRED — ANYONE CAN ACCESS
341 MALICIOUS SKILLS DISCOVERED ON CLAWHUB
SHARED DATABASES LEAK DATA BETWEEN TENANTS
Security & Privacy

Your data stays yours.
That's the deal.

Every KillerBot instance is isolated, encrypted, and yours alone. We don't read your conversations. We don't train on your data. We don't share your infrastructure.

Not because we wrote a nice privacy policy. Because the architecture makes it impossible.

Isolated Instances

Every customer gets their own container. Not a row in a shared database — an actual, separate machine. Your neighbor's AI can't see your data because it doesn't exist in the same universe.

Zero Shared Data

No shared databases. No shared storage. No shared compute. Your conversations, files, and agent memory live on your instance and nowhere else. We never use your data to train models.

Your Keys, Your Control

API keys are encrypted and stored on your instance. We never have access to them. Delete your instance, everything goes with it. No backups of customer data on our side.

Infrastructure security

AES-256 encryption at rest. TLS 1.3 in transit. Firewalls locked to port 443. Dedicated Fly.io machines per customer — no shared anything. API keys encrypted on your instance. We never see them.

Learn more about infrastructure

Privacy by design

We collect the minimum: your email for auth (via Clerk), your payment info (via Stripe). That's it. Your conversations, files, API keys, memory — all of it stays on your instance. We never use your data to train AI models. Delete your instance, it's gone.

Learn more about privacy

Incident transparency

When something goes wrong, we tell you. No burying it, no vague statements three weeks later. We publish what happened, how we responded, and what we changed.

View incident history

The problem with self-hosted AI

Most self-hosted AI setups are held together with duct tape and good intentions. Here's what we keep seeing:

Open instances with no authentication — anyone on the internet can walk in

API keys hardcoded in plaintext config files, committed to public repos

Shared databases with tenant IDs pretending to be "isolated"

No encryption, no monitoring, no automatic updates — just vibes

Sound familiar? Yeah, it scared us too.

What we did about it

Not a whitepaper. Not a checkbox exercise. Actual engineering decisions that make every KillerBot instance secure by default.

True single-tenant

Your own container. Not a row in our database — an actual, isolated machine. Your neighbor's AI assistant literally cannot see your data because it doesn't exist in the same universe.

Encrypted everything

AES-256 at rest. TLS 1.3 in transit. Your conversations are encrypted before they hit disk and encrypted again on the way to your device. Belt and suspenders.

No shared infrastructure

Dedicated compute, storage, and network per user. Not "dedicated" with air quotes — actually dedicated. Your instance runs on its own machine.

Curated skills only

No third-party marketplace free-for-all. Remember the "ClawHavoc" campaign? 341 malicious skills found on ClawHub, siphoning API keys and conversation history. Yeah, we don't do that.

Automatic security patches

We update so you don't have to. No "please manually upgrade to fix this critical vulnerability" emails. Patches roll out automatically, zero downtime.

Zero data training

Your conversations never train models. Not ours, not anyone else's. We pinky-promise, and also it's in our terms of service and architecture — the data literally doesn't flow there.

Open source foundation

No mystery boxes. Built on open-source tools and frameworks you can audit yourself. We don't hide behind proprietary walls because we don't need to.

See for yourself

Three users, three completely separate worlds. No shared anything.

🔒 FIREWALL — PORTS 443 (HTTPS) ONLYUser 1ComputeIsolated containerStorageAES-256 encryptedNetworkTLS 1.3User 2ComputeIsolated containerStorageAES-256 encryptedNetworkTLS 1.3User 3ComputeIsolated containerStorageAES-256 encryptedNetworkTLS 1.3Firewall-protected isolation — no shared infrastructure

For the technical folks

You want specifics. We respect that. Here's the nitty-gritty.

Network firewallPort 443 only — all other ports blocked
Transport encryptionTLS 1.3 everywhere
At-rest encryptionAES-256
Instance isolationDedicated Fly.io machines per customer
Database isolationNo shared databases — period
AuthenticationGateway authentication required for all connections
Penetration testingRegular testing (planned)
ComplianceSOC 2 Type II (in progress)

Want to dig deeper? We're happy to talk security with your team. security@killr.bot

Security FAQ

Common questions about how we protect your data.

Every KillerBot customer gets a completely isolated instance — separate runtime, separate storage, separate encryption keys. Your data never shares infrastructure with other users. It's full tenant isolation, not just database-level separation.
No, never. Your conversations, files, and personal data are never used to train, fine-tune, or improve any AI models. We also ensure our upstream AI providers (OpenAI, Anthropic, Google) do not train on your data through their API terms.
We maintain a documented incident response plan. In the event of a breach, affected customers are notified within 72 hours with full transparency on scope and impact. You can report vulnerabilities to security@killr.bot.
All API keys, tokens, and secrets are encrypted at rest using AES-256 and never logged or exposed in plaintext. Secrets are injected at runtime into your isolated instance and are never accessible to other customers or our own staff.
We use AES-256 encryption for data at rest and TLS 1.3 for data in transit. All backups are encrypted, and encryption keys are managed per-tenant so that no single key compromise can affect multiple customers.
Yes. You can request a full data export at any time, and we support complete account deletion that permanently removes all your data, conversations, files, and configuration from our systems within 30 days.
KillerBot targets 99.9% uptime for all paid plans. Your isolated instance runs on redundant infrastructure with automated failover. We publish real-time status at status.killr.bot.
All skills and plugins go through a security review before being made available. They run in sandboxed environments with limited permissions, and each skill explicitly declares what data it can access. We audit skill behavior regularly.

Try it free.
If you can hack it, tell us.

7 days free. Your own isolated instance. Encrypted everything. Zero data training. We're not asking you to trust us — we're asking you to verify.

Start Free TrialView Pricing

Found a vulnerability? We'd genuinely love to hear about it. security@killr.bot