Start with where a startup is exposed
A startup's risk sits in a handful of systems: the cloud account that runs the product (AWS, Google Cloud, or Azure), the place everyone signs in (Google Workspace or Microsoft 365), the code on GitHub, the platforms you deploy on, and the laptops your team works on. A leaked password, a risky permission change, a secret pushed to a repository, or a stolen laptop each shows up in one of them.
The practical starting point is visibility. Collect the security events those systems already record, have something watching them at all hours, and decide who approves a response. The startup cybersecurity checklist covers the rest, stage by stage.
- AWS, Google Cloud, or Azure: who changed permissions, which APIs were called, and what happened to servers and storage.
- Google Workspace or Microsoft 365: who signed in, from where, and what admins changed.
- GitHub: leaked secrets, vulnerable dependencies, and changes to branch protection or members.
- Vercel, Supabase, Railway, and Cloudflare: who read or changed secrets, who joined, and what was opened to the internet.
- Laptops and servers: sign-ins, new admin accounts, and suspicious commands.
One security platform for startups, not five tools
Startup cybersecurity solutions usually arrive in pieces: a place to keep logs, a tool that raises alerts, a queue for the response, and a compliance tool for the audit. Each piece needs someone to read it, and the person reading is usually also shipping the product.
Jutsu puts the four jobs in one place. It collects the security events from the systems you connect, detects threats in them, proposes or runs the response, and keeps the record of all of it as compliance evidence. One alert is investigated, answered, and filed once, instead of being copied between tools.
- Monitoring: security events from your cloud, sign-in, code, and deploy platforms, and from laptops and servers, watched around the clock.
- Threat detection: built-in rules for each source, with AI triage and threat-intelligence lookups on every alert.
- Response: fixes such as blocking an IP or disabling a user, run on your approval or within policies you set.
- Compliance evidence: the records of that work, plus policy drafts and evidence tasks on every paid plan.
What you can connect today
Jutsu monitors the sources you connect, and nothing else. Each connection in the table below has a step-by-step setup guide, and security monitoring for startups lists what to watch and alert on in each one.
Microsoft 365 sign-ins and Wazuh alerts can be connected too, and anything that can make an HTTP request, such as a syslog daemon, can send logs to a webhook. Connectors for Splunk, Microsoft Sentinel, CrowdStrike, and Elastic are on the roadmap, not available today.
What happens to an alert
Every event that enters Jutsu goes through the same steps, run by AI agents.
- Sort: each alert gets a category, severity, risk score, and verdict.
- Look up: IP addresses, domains, and file hashes are checked against threat intelligence such as VirusTotal, AbuseIPDB, AlienVault OTX, GreyNoise, MalwareBazaar, Kaspersky OpenTIP, MISP, CISA KEV, and IP-API geolocation.
- Group: related alerts become one incident, so you read one story instead of a pile of alerts.
- Act: Jutsu proposes a fix, such as blocking an IP or disabling a user, in AWS, Google Cloud, Azure, Google Workspace, Microsoft 365, and the platforms you deploy on.
- Report: incident reports and SOC activity reports are written for you.
No security team needed to start, and you stay in charge
You don't need a security team to start. The AI agents do the repetitive work: reading, looking up, sorting, and grouping alerts. Decisions that need judgment stay with your team. On a small team, the person who approves a response can be the CTO or the engineer on call. Jutsu is software: nobody at Jutsu watches your alerts for you.
- When the AI isn't sure about an alert, it asks a person instead of acting.
- On the Startup plan, a person approves each action before it runs.
- On the Growth plan, actions your policies allow can run on their own.
- Every action is recorded, and actions such as blocking an IP, isolating a server, or disabling a user can be undone.
Security work that doubles as SOC 2 evidence
Larger customers ask startups how they monitor and respond to security events, and a SOC 2 audit asks for proof. Jutsu keeps a record of alerts, investigations, and response actions, and writes incident and SOC activity reports. Every paid plan also includes the Compliance module, which drafts your policies and sets up recurring evidence tasks for SOC 2 and 12 other frameworks. SOC 2 for startups explains how the two fit together.
Where Jutsu fits, and where it doesn't
Jutsu fits a startup that runs on the systems above and wants monitoring, investigation, and response in one place, with prices it can read before a sales call: Free ($0/month), Startup ($149/month), Growth ($499/month), Enterprise (custom quote).
It does not replace the basics every team still has to do: turning on multi-factor authentication, limiting admin access, patching, and keeping backups. It doesn't scan your code itself (GitHub's own secret scanning, code scanning, and Dependabot alerts flow in), and it doesn't cover prompt injection or other risks in the AI models your product uses. For those, start with the OWASP Top 10 for LLM applications. And it sees only what you connect.
