IN SCOPE
Microsoft Azure
Read-only extraction of your resources, network paths and configuration, built on the Azure Resource Graph. This is what is being built right now.
Work in progress · Early stage
Sweep the stack. Surface the flaws.
Saktori connects to your cloud provider, pulls the architecture of everything you've deployed, and runs an AI sweep across the whole picture — surfacing misconfigurations and attack paths before an attacker reads them for you.
READ-ONLY BY DESIGN · OPEN SOURCE · AZURE FIRST
How it sweeps
Three passes. No ceremony.
From an empty terminal to your first findings, without writing a line of configuration. That's the whole pitch.
- PASS 01
Connect the cloud
Point Saktori at your Azure subscription with read-only credentials. No agents to deploy, no scripts to maintain — it looks at your infrastructure, it never touches it.
SCOPE: AZURE · READ-ONLY
- PASS 02
Map the topology
Resources, network paths and configuration are pulled automatically. Saktori builds the full picture of what is actually deployed — not what the whiteboard claims.
SOURCE: RESOURCE GRAPH
- PASS 03
Run the sweep
The AI reads the architecture like an attacker would: exposed surfaces, risky relationships, silent misconfigurations — surfaced as findings with context, not a wall of raw rules.
OUTPUT: CONTEXTUAL FINDINGS
Coverage
Azure is the first contact.
Saktori starts with a single, deeply-built integration instead of three shallow ones. The radar stays on — more clouds come into scope as the detection engine matures.
ON THE RADAR
Amazon Web Services
Queued. The detection engine is provider-agnostic at its core — AWS comes into scope once the Azure integration proves the concept.
ON THE RADAR
Google Cloud
Queued. Community demand sets the order of the queue — open an issue and make the case for your cloud.
* PROVIDER PRIORITY IS SHAPED IN THE OPEN — ISSUES ARE VOTES.
Open source
Built in the open, from day one.
A security tool should earn trust the same way it finds flaws: transparently. Saktori's code is public, its roadmap is public, and its rough edges are public. Early stage means your issues and PRs actually move the needle — star the repo and watch the sweep take shape.
→ https://github.com/astrophe-dev/saktori
- EARLY STAGE
- APIS IN MOTION
- DOCS CATCHING UP
- ROADMAP PUBLIC