Aurascape
September New Innovations Recap: More Precise Protection for AI Work (2026-10-05) commercialThe section your link pointed to isn't on Aurascape's page any more, so we've brought you to the top.
Aurascape secures employee AI use, helps teams build agents safely, and protects AI agents in production with real-time visibility, policy enforcement, and data protection.
Summary
Aurascape is a commercial ai-security platform that provides real-time visibility, intent-based controls, and protection for every AI interaction. It is run as a service and is for platform engineers, specifically for securing shadow-ai usage. Its documentation positions it alongside tools managing tool access, focusing on inspecting tool calls down to parameters and detecting prompt injectionprompt injectionAn attack where text the model reads, such as a web page, file or tool result, carries instructions that override the user's. It is the main security risk for agents with tools. in documentation. Since its launch in 2023, the project has seen eight releases within the tracked window.
Aurascape secures employee AI use, helps teams build agents safely, and protects AI agents in production with real-time visibility, policy enforcement, and data protection.
How Aurascape helps
Which AI agents and tools are running in my environment without ever having been registered?
discovers MCP servers and tools automatically and enrolls them on sight, so shadow-ai surfaces show up without hand-maintained allowlists
Which of my agent's tool calls actually went through approved governance, and which slipped past it?
marks every call approved by the gateway and flags any tool invocation reaching the model that didn't carry that mark
Is a coding assistant session about to leak a secret or run something destructive?
inspects live streaming traffic from assistants like Claude Code, Copilot, and Cursor inline, catching pasted credentials and blocking or holding destructive shell commands and git pushes before the client executes them
Is a model being steered by instructions hidden in documentation or MCP output?
scans READMEs, docs, and MCP outputs for injected instructions and neutralizes them before the agent acts on them
Who can call which MCP tools, and what happens when someone shouldn't?
binds tool-level sanctioning to users and groups and applies configurable actions — coaching, hold-for-approval, or block — when a call violates policy
Can I reconstruct exactly what happened in an AI conversation for an investigation or audit?
keeps audit-ready logs of prompts, responses, connections, and tool calls behind each policy flag, accessible under role-based access control
Languages
Screenshots
From the release notes, newest first. Click one to see it full size.Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for Aurascape, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Aurascape puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Website history
aurascape.ai, every changeAurascape's home and product pages and 11 more pages as they looked each month from April 2024 to October 2026: 23 renders, 8 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Coverage
Missing something? Tell us
What Aurascape connects to, runs on and detects, read from its release notes and docs. So far: 2 updated integrations.
2 changes, tracked since Oct 5, 2026.
-
Oct 52026
updated Granular model-level access policy for Claude, Anthropic API, ChatGPT, OpenAI API, Google Vertex AI API, and Amazon Bedrock
September deepens that coverage with more granular model-level controls for Claude, the Anthropic API, ChatGPT, the OpenAI API, Google Vertex AI API, and Amazon Bedrock.
-
Oct 52026
updated Expanded MCP conversation record detail via Zero-Bypass MCP Gateway
With Model Context Protocol (MCP)
The records also show more response content from interactions that use Model Context Protocol (MCP). For traffic monitored by the Zero-Bypass MCP Gateway, process name details help analysts attribute an interaction to the specific local application or agent behind it.
Chat & assistant apps 1
Agent frameworks & SDKs 1
Model providers & gateways 5
Endpoint & network security 1
Nothing first seen in this window. That doesn't mean Aurascape shipped nothing, only that we found no record of it.
How we count
Read from 1 of 4 release notes and docs updates we hold for Aurascape. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Aurascape's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
4 entries
No entries match these filters.
- October 20261
- September 20262
- August 20261
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.