Enterprise-grade cybersecurity. Built for startups

Protect your cloud, your applications, and your team's identities without building a security team. Jutsu is one platform for monitoring, threat detection, response, and compliance evidence: it watches AWS, Google Workspace, GitHub, and laptops around the clock, AI agents check every alert, and nothing is blocked or disabled without your approval or a policy you set.

Jutsu dashboard
Jutsu · SOC overview
  • AWS, Google Workspace, GitHub, laptopsPlus Azure, Google Cloud, Microsoft 365, Vercel, Supabase, Cloudflare, Railway, and your servers.
  • AI takes the first lookEach alert gets a category, severity, risk score, and verdict before anyone opens it.
  • You make the callFixes run on your approval or within policies you set, and they can be undone.
  • SOC 2 evidence as a by-productThe same records support SOC 2 readiness when a customer asks.

What cybersecurity does a startup need?

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.

What Jutsu monitors today

Each row is a documented connection with its own setup guide.

SourceWhat it coversWhat Jutsu collectsSetup
AWS CloudTrailCloud accountAWS API calls, console sign-ins, and resource changes, from the CloudTrail log files of the trails you choose.CloudFormation stack, no access keys
Microsoft AzureCloud accountEach subscription's Activity Log and the alerts from Microsoft Defender for Cloud, read by 19 built-in Azure rules.About 10 minutes, read-only roles
Google Cloud PlatformCloud accountCloud Audit Logs: Admin Activity, System Event, and Policy Denied, plus Data Access where you have turned it on.About 10 minutes, keyless
Google WorkspaceSign-in and adminSign-ins and Admin console changes by default. Drive activity and third-party app grants if you turn them on.About 10 minutes
GitHubCodeSecret scanning, code scanning, and Dependabot alerts, pushes, branch protection and repository changes, and member and team changes.About 5 minutes, read-only app
VercelDeploy platformThe team activity feed: environment variable reads and writes, deployments, member and role changes, and token creation.About 5 minutes
SupabaseDatabase and authThe Auth and Postgres logs of every project, and a change feed of members, MFA, projects, API keys, SSL, and network restrictions.About 5 minutes, read-only token
RailwayDeploy platformThe workspace audit log: shell and exec access into containers, variable and secret changes, deployments, and membership changes.About 2 to 5 minutes
CloudflareEdge and accessThe account audit log, firewall events for your zones, and Zero Trust Access logins.About 10 minutes, read-only token
macOS hostLaptopsSecurity-relevant unified-log events, EndpointSecurity process activity on macOS 13 and later, and osquery checks.One install command per Mac
Windows hostLaptops and serversSecurity and System event logs, Sysmon events when Sysmon is installed, and osquery checks.About 10 minutes per host
Linux hostServersSign-in and sudo events, including SSH, logins, and cron, syslog from other devices if you turn it on, and osquery checks.About 10 minutes per host
Docker containersContainersThe stdout and stderr of the containers on a Docker Engine host, buffered on disk if the connection drops.About 5 minutes per host
WazuhExisting detectionWazuh alerts, sent by a forwarder on your Wazuh manager.Forwarder install
WebhookAnything elseSyslog, JSON, and plain-text logs posted over HTTPS by rsyslog, syslog-ng, Fluent Bit, Vector, curl, or any other sender.About 5 minutes, plus your sender

Visibility is limited to the sources you connect. Microsoft 365 sign-ins can be connected as well. Splunk, Microsoft Sentinel, CrowdStrike, Elastic, and other SIEM connectors are on the roadmap.

Three steps, end to end

  1. Connect your first source

    Start with Google Workspace, AWS, or GitHub, or install the agent on a laptop. Most take about 10 minutes.

  2. AI checks every alert

    Alerts are sorted, looked up against threat intelligence, and grouped into incidents around the clock.

  3. You approve what matters

    Jutsu proposes the fix and your team approves it. When the AI isn't sure, it asks a person.

What a startup gets with Jutsu

  • Cloud account monitoring

    AWS CloudTrail, Google Cloud audit logs, and Azure Activity Logs: permission changes, API calls, and resource changes.

  • Sign-in and admin monitoring

    Google Workspace and Microsoft 365 sign-ins and admin changes, with Drive activity and app grants as options in Workspace.

  • GitHub security events

    Secret scanning, code scanning, and Dependabot alerts, with repository and membership changes.

  • Deploy platforms and databases

    Vercel, Railway, Supabase, and Cloudflare: secret reads and changes, members, deployments, and firewall events.

  • Laptops and servers

    Windows event logs, Linux sign-ins and sudo, and macOS process activity, with osquery checks on each.

  • AI triage, approved response

    Every alert sorted with a verdict and threat intelligence. Fixes run on your approval or policy and can be undone.

Common questions

What cybersecurity does a startup need first?

Start with visibility into the systems you run on: your cloud account (AWS, Google Cloud, or Azure), where your team signs in (Google Workspace or Microsoft 365), GitHub, and your team's laptops. Collect their security events, have them watched around the clock, and decide who approves a response. Jutsu covers that monitoring, triage, and response for the sources you connect.

Do we need to hire a security engineer to use Jutsu?

No. You don't need a security team to start. Jutsu's AI agents do the routine monitoring, investigation, triage, and reporting. They don't replace the people who own security decisions: your team stays responsible for policies, approvals, and business context. Jutsu is software, so nobody at Jutsu watches your alerts for you.

Which systems can Jutsu monitor today?

Jutsu connects today to AWS CloudTrail, Microsoft Azure, Google Cloud, Google Workspace, Microsoft 365, GitHub, Cloudflare, Vercel, Supabase, Railway, and Wazuh. Windows, Linux, and macOS hosts connect through the Jutsu agent, and Docker containers through a collector on the Docker host. Syslog, and anything else that can make an HTTP request, can send logs to a webhook. Splunk, Microsoft Sentinel, CrowdStrike, Elastic, and other SIEM connectors are on the roadmap.

How long does setup take?

Each documented connection takes about 10 minutes or less. Installing the Jutsu App on a GitHub organization takes about 5 minutes, and so does connecting Vercel or Supabase. Railway takes about 2 minutes with Connect with Railway. Google Cloud, Google Workspace, Microsoft Azure, and Cloudflare take about 10, and AWS connects with a CloudFormation stack and no access keys. A Windows or Linux host takes about 10 minutes per host, and a Docker host about 5.

Can Jutsu take action on a threat?

Yes, within the limits you set. 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.

Does Jutsu help with SOC 2?

Yes. Jutsu provides: an audit trail of alerts, investigations, and response actions; incident reports and SOC activity reports; and, on every paid plan, the Compliance module for SOC 2, ISO 27001, and 11 more frameworks: policy drafts, recurring evidence tasks, a readiness score, and checks on connected systems that feed those tasks. The checks run every day on AWS, Google Cloud, GitHub, Google Workspace, Cloudflare, Vercel, Railway, and Windows, Linux, and macOS hosts, and cover Microsoft Azure and Supabase as well. Jutsu supports readiness and evidence collection. Your team and your auditor remain responsible for the audit, and Jutsu does not guarantee an audit outcome.

Does Jutsu protect our AI features from prompt injection?

No. Jutsu watches the systems your product runs on, such as your cloud account, GitHub, and the platforms you deploy on. It doesn't inspect what goes into or comes out of an AI model. For prompt injection and other model risks, start with the OWASP Top 10 for LLM Applications.

What does it cost?

The Free plan costs $0 with no credit card. It covers 5 assets and 50 AI investigations a month, with limited AI triage. Paid plans are published: Free ($0/month), Startup ($149/month), Growth ($499/month), Enterprise (custom quote).

Start with the security your startup needs now

Connect your first source on the Free plan with no credit card, or book a demo.

Subscribe to our newsletter

Get the latest security tips, product updates, and news delivered to your inbox.