What's new at Spoorder
Platform updates, engine releases and framework additions, newest first.
Nov 16, 2026
EngineForge (LLM red team) on Pro, priced by depth
Forge (LLM red team) is now available on Pro, Scale and Enterprise. A run costs 10 credits at Quick depth, 25 at Standard and 60 at Deep. The credits are taken when the run starts and given back if it cannot start, fails or times out, and the credit history shows the depth.
Nov 16, 2026
IntegrationLinear issues from findings; Jira and Linear on Pro and above
An owner or admin can connect Linear with a Linear API key and choose the team that issues go to. Create a Linear issue from a finding with its severity, location and fix guidance filled in. Every 4 hours, and on demand, a sync moves a finding to awaiting verification when its Linear issue is done or canceled. Connecting Jira or Linear, syncing and creating issues from findings are included on Pro, Scale and Enterprise.
Nov 15, 2026
AIAI bill of materials
Outputs has a new AI-BOM: the AI packages your code uses and the model providers they send data to, MCP servers, model files in your repositories, AI services in connected AWS, Azure and Google Cloud accounts, and chat assistants and AI endpoints that Strike found on your sites. Secrets scans of a repository now check MCP configuration files for written-in secrets, plain HTTP servers, unpinned packages, file access to the whole disk or home folder, and tools that run without approval, and report model files in formats that run code when loaded. Export the AI-BOM as CycloneDX 1.7. SBOM and CBOM exports are now CycloneDX 1.7 as well (SBOM also as SPDX 2.3), checked against the official schema.
Nov 15, 2026
ComplianceAI evidence pack; compliance reports cost no credits
From the AI-BOM you can export an AI evidence pack as JSON or Markdown. It lists, for each control of the OWASP Top 10 for LLM applications and for agentic applications (2026), NIST AI RMF, ISO/IEC 42001 and the EU AI Act, the evidence Spoorder has recorded and the open findings that are gaps. It is evidence for your own assessment, not a statement of compliance. Compliance reports are included in your plan and cost no credits.
Nov 15, 2026
PlatformTrust Centre on trust.spoorder.com or your own domain
Published Trust Centres are served at trust.spoorder.com/your-page. On Scale and Enterprise you can use your own domain: enter it on the Trust Centre page, add the TXT record shown there to your DNS, check it, then email support@spoorder.com and we send you the CNAME record that points the domain at your Trust Centre. Only the Trust Centre page is served on these addresses, never the dashboard or sign-in.
Nov 15, 2026
SecuritySign-up and sign-in
Sign-up no longer accepts addresses at throwaway email services. When your organisation requires two-factor sign-in, signing in through your organisation's own SSO meets that requirement, because your identity provider handles the second factor; password sign-ins still need two-factor.
Nov 15, 2026
IntegrationCircleCI, Jenkins and GitLab templates fixed
The CircleCI orb and the Jenkins step now start a scan with the Spoorder CLI, wait for it and, when you give a gate, fail the build if the gate fails. The GitLab CBOM template posts to the right address. All of them read the API key from the environment, and a key with the scan scope can now also generate a CBOM.
Oct 8, 2026
BillingTrials start with a card; confirm your email to scan
A 14-day trial of Builder, Pro or Scale now starts at Stripe with a card. Nothing is charged until the trial ends, and you can cancel before then. A trial includes 100 credits; the plan's full monthly credits start with the first payment. New accounts confirm their email address before their first scan. Gate (pipeline security) scans cost 4 credits and run in the scan queue; the API returns the scan id. Each plan has a daily scan limit: Free 5, Builder 50, Pro 200, Scale 500, Enterprise 2,000.
Oct 6, 2026
BillingCredits reset on your billing date; clearer prices for AI
Plan credits now reset on your own billing date (the day your plan renews, or your sign-up day on Free) instead of the 1st of the month; Billing shows the date. An AI pentest is priced by depth: Quick 40, Standard 120 or Deep 250 credits, with 4 runs a month on Pro with the Scale engine pack and 10 on Scale. Live app scans no longer have a monthly limit. AI fixes count against your plan's monthly allowance and then cost 8 credits; AI triage and enrichment cost 1 credit per finding, AI summaries and AutoFix pull requests 5. A scan whose main scanner could not run is not charged. Top-up packs are now 100 credits for $12, 500 for $49 and 2,000 for $159.
Oct 6, 2026
PlatformPlan changes and data retention, with notice
After a downgrade, scheduled scans the new plan does not include are paused and start again by themselves if you upgrade; API keys are kept but refused without API access; single sign-on stays on for 14 days before it turns off. Owners and admins are emailed what changed. Each plan's data retention now applies, after 30 days' notice on Billing, the dashboard and by email; open findings are never deleted. The /api/v1/dast endpoints were removed: start a live app scan with POST /api/v1/scan/start.
Oct 2, 2026
PlatformAutomation rules
Under Integrations, Automation Rules you can create rules that act when a critical or high finding is created, an SLA deadline is breached or a scan finishes. A rule can post to your saved Slack webhook, create a Jira issue or call one of your saved webhooks, and each rule shows its recent runs. Up to 50 rules per organisation.
Oct 2, 2026
EngineRepository scans: commit history, depth and filters
A secrets scan of a saved repository reads the commit history from our own copy of the repository, so it works for private repositories too: the last 100 commits at Standard depth and the full history at Deep. Code and dependency scans of saved repositories follow the depth, minimum severity, path exclusion and EPSS settings. A scan that left files or findings out is shown as incomplete and does not close earlier findings. Checking a found secret against its provider happens only when you tick the box.
Oct 2, 2026
PlatformSBOM history and compare
The SBOM Centre keeps up to 30 snapshots per project, saved when you export or when a dependency or container scan completes. Pick two to see which components were added, removed, changed version or became vulnerable.
Oct 2, 2026
PlatformAccepting a risk records who and why
Accepting a risk now needs a written reason. The finding history, the risk register and the audit log show who accepted it and when, and note when that person also owns the item. Approved policies show who approved them.
Oct 2, 2026
SecurityStricter script policy in the app; accessibility statement
The signed-in application and the sign-in pages are served with a per-request script nonce, so an injected inline script does not run. An accessibility statement at /legal/accessibility says what we test and what is not done yet.
Oct 2, 2026
IntegrationYour own Gemini key, saved project CI settings, working SARIF and Snyk imports
An admin can save the organisation's own Google Gemini key for the AI analysis step of AI pentest scans; it is stored encrypted and never shown again in full. CI settings saved on a project are used as defaults by repository scans. SARIF and Snyk result imports are accepted again.
Oct 2, 2026
PlatformFindings on branches and pull requests
A finding seen only on a pull request or side branch closes when that branch no longer reports it, or after 30 days without a scan of that branch. A stale branch no longer reopens a finding the default branch has fixed.
Oct 2, 2026
ComplianceFramework catalogues checked against the published standards
Control titles and descriptions for all eight frameworks were checked against the published text, missing controls were added and a few identifiers were corrected. Existing evidence moves with its control. Because the catalogues now list more controls, a framework's coverage percentage can read lower than before until evidence is added for the new ones.
Oct 2, 2026
EngineScan a saved private repository from the dashboard
Code, dependency and secrets scans of a saved repository now run as server-side jobs with the credential saved on the repository, so private repositories work from the dashboard. These scans count toward plan limits, keep running if you close the page and can be cancelled. For secrets, the depth sets how much commit history is read.
Oct 2, 2026
PlatformDuplicates are counted once; reopened findings go back to the right queue
When two engines report the same issue, the duplicate is closed with a note that points to the original, so open counts are not doubled. A finding that is reopened after being marked false positive or accepted returns to triage, and one reopened after a fix returns to the Fixes board. A scan of a pull request or side branch no longer closes findings that belong to the default branch.
Oct 2, 2026
PlatformCVE watch list is re-checked every day
Packages on your CVE watch list are checked daily against new advisories, and you get one in-app alert per day listing what is new. The alert can be switched off under notification settings.
Oct 2, 2026
SecuritySign-in and integration hardening
Two-factor codes and backup codes are verified with a limit on attempts per account, and each backup code works once. Addresses you enter for Jira, webhooks, Teams, Slack and self-hosted Git are checked before the platform calls them. SSO settings have an allowed email domains field that applies to every SSO sign-in.
Oct 2, 2026
PlatformCredits: published prices everywhere, refunds when a scan cannot run
Repository, container registry and cloud account scans charge the published price and return the credits when the scan fails, times out or has nothing to scan. An AI pentest costs 40, 120 or 250 credits by depth (Quick, Standard, Deep) and an AI fix 8, as listed in the FAQ.
Oct 2, 2026
UXFixes, Compliance and Risk show the plan they need
On Free and Builder, opening Fixes, Compliance or Risk shows which plan includes it instead of an empty page. The controls library and SLA policies stay available on Builder.
Oct 2, 2026
IntegrationStart scans and evaluate gates from a pipeline
An API key with the scan scope can now start a scan and evaluate a security gate, so a pipeline step can gate a release on scan results. Gates honour their mode: a blocking gate fails the step, a warn gate reports failures without failing it, and a report gate only records the result. Gates limited to certain projects or scan types are skipped for other scans.
Oct 2, 2026
PlatformPlan limits apply when you add targets and schedules
Adding a target or a scheduled scan beyond the number your plan includes is refused with a message that says what the plan includes. Anything you already have stays. New accounts start with their plan's monthly credits.
Oct 2, 2026
PlatformAccepted risk can carry a review date
When you accept the risk on a finding you can set a date. On that date the finding reopens, with an entry in its history.
Oct 2, 2026
ComplianceTrust Centre: approve or decline document requests
Requests for documents marked "On request" now appear on the Trust Centre page. Approving one emails the requester a download link that works for 7 days.
Oct 2, 2026
PlatformScheduled scans run through the same checks as manual scans
A scheduled scan is now launched the same way as a manual one, so credits, plan limits and target checks apply to both. The Scheduled Scans panel shows why a run was not started. Strike (Live app testing) and Pulse (Health check) can be scheduled, and a schedule that fails to start five times in a row is switched off.
Oct 1, 2026
PlatformOne definition of open and resolved across every page
The dashboard, findings list, team view, sidebar badge and release gates use the same definitions of open, resolved and awaiting triage, so counts match wherever you look.
Oct 1, 2026
UXFinding history timeline and a Reopen button
Each finding page shows who changed its status, when, and the note they left. A verified or accepted finding can be reopened from the same page. Dashboard tiles open the findings list with the filter they count by, and a bar shows which filters are active.
Oct 1, 2026
PlatformRe-tests end as verified, reopened or inconclusive
A complete re-test of the same target that no longer detects the issue marks the finding verified. A re-test that detects it again reopens the finding. A re-test that could not run to completion is recorded as inconclusive and leaves the finding as it was. Results from Verify fix are recorded when the scan finishes.
Oct 1, 2026
ComplianceFramework scores read "Not assessed" until there is evidence
Framework coverage counts controls that have been assessed, and a framework with no evidence reads "Not assessed" instead of a percentage. Audit Prep describes the state of your evidence: Evidence healthy, Gaps to close or Not assessed. Edits on the Security Controls page are saved, role-checked and written to the audit log.
Oct 1, 2026
UXTrial accounts show their trial plan; first-run setup keeps its place
An account on a 14-day trial of Builder, Pro or Scale shows that plan, its limits and the trial end date, with a Subscribe button on the billing page. The onboarding wizard keeps your progress during the session, a free health check runs on a registered target before ownership is verified, and the Targets page has a visible Verify ownership action.
Oct 1, 2026
PlatformTrust Centre documents open through an access-checked download link
Documents on a Trust Centre page are served through a download link that checks access and expires after five minutes. Visitors can send a document access request without an account. Requests are recorded; approving them is still a manual step.
Sep 30, 2026
PlatformScans run as server-side jobs, with one results page
Pulse (Health check), Strike (Live app testing), API, resilience and paste-mode code scans start on the server and the page follows their progress, so you can close the tab and come back to the results. A single results page covers running, queued, partial, failed and cancelled scans, and Scan Compare uses the baseline you choose.
Sep 30, 2026
PlatformOrganisation switcher
People who belong to more than one organisation can switch between them from the avatar menu. Data and role follow the organisation selected.
Sep 30, 2026
SecurityTwo-factor setup, MFA policy and account settings
The QR code on the 2FA setup page is drawn in your browser. When an organisation requires MFA, members who have not enrolled are taken to setup first. Notification toggles in Settings control which notifications you receive, and you can delete your personal account once any organisation you own has been transferred.
Sep 30, 2026
UXAccessibility pass across the dashboard
Dialogs keep keyboard focus and close with Escape, controls are reachable by keyboard and labelled for screen readers, a skip link leads the dashboard, text is at least 11px, and text contrast was brought to WCAG AA.
Sep 30, 2026
PlatformReports and SBOM exports
Compliance reports are built from your framework catalogue, evidence and scores, and export as JSON or Markdown. SBOM export is available as CycloneDX 1.5, SPDX 2.3 or JSON from dependency and container scan results. The vulnerability report covers the period you select.
Sep 29, 2026
EnginePartial coverage is shown as partial
When one of the scanners behind an engine is unavailable for a run, the scan is marked Partial and names what did not run, in the live view and in scan history.
Sep 29, 2026
PlatformPlan limits apply the same way everywhere; trials start at signup
Engine access follows your plan wherever a scan is started, and the engine catalogue shows the plan each engine needs. Choosing Builder, Pro or Scale at signup starts a 14-day trial of that plan.
Sep 29, 2026
SecurityActive scans are tied to verified targets
Active engines start only against a target whose ownership has been verified, and the URL scanned must be on that host. Changing a target's host asks you to verify again. Passive checks such as the basic health check do not need verification.
Jul 5, 2026
PlatformKnowledge base: 49 new entries
The vulnerability knowledge base gained 49 entries across injection, access control, cryptography, API and mobile categories, each with how-to-fix guidance shown on matching findings.
Jul 1, 2026
PlatformEPSS and CISA KEV on findings, with Fix now, Fix soon and Watch
Findings with a known CVE carry their EPSS score and CISA KEV status. A priority score built from KEV listing, severity, EPSS and reachability sorts findings into Fix now, Fix soon and Watch.
Jun 30, 2026
ComplianceRisk Matrix and a single Outputs section
A 5x5 likelihood by impact matrix shows where the risks in your register sit. Reports, the Evidence Vault, the Evidence Pack and the Trust Centre now live together under Outputs.
Jun 29, 2026
PlatformVerify fix and Markdown export
Start a verification scan for selected findings from the finding page or the Fix board. Pages that export PDF, CSV or JSON also offer a Markdown export, including scan results, the risk register and the Fix board.
Jun 27, 2026
UXOnboarding wizard for new accounts
A new organisation is guided through creating a project, adding a target and running a first scan, instead of landing on an empty dashboard.
Jun 26, 2026
PlatformScheduled Scans panel
Schedules have one home under Scans: a table of schedules with next run time and status, a form to create one for a project and target, and an on/off switch for each.
Jun 18, 2026
UXNew visual design
The dashboard and the public site moved to a single teal theme with solid card backgrounds and more legible text. Mobile navigation and the pricing section were fixed at phone width.
May 24, 2026
EngineAuthenticated scanning with saved credentials
Save a login for a target once and choose it when you start a Strike (Live app testing) scan. Supported methods include bearer token, cookie and form login, and saved values are resolved on the server.
May 18, 2026
IntegrationBitbucket and Azure DevOps connections
Connect Bitbucket and Azure DevOps alongside GitHub and GitLab, and pick repositories from a connection when you add a code target.
May 5, 2026
UXFindings list in columns; AI pentest shows live progress
The findings list has columns for severity, status, triage, SLA and assignee, with knowledge base guidance one click from the title. AI pentest scans report their progress while they run.
May 4, 2026
UXTriage from the All Findings page
Findings awaiting triage can be confirmed, marked false positive or accepted from the findings list. A false positive needs a written reason of at least 20 characters.
May 3, 2026
CompliancePolicy register with review reminders
Record policies with versions, approval and a review cycle. Daily reminders for policy, vendor, continuity plan and evidence reviews that are coming due can be sent to Slack or Teams.
May 2, 2026
PlatformTrust Centre public page
Publish a public Trust Centre page with your branding, security overview, documents, subprocessors and FAQ. Visitors can request access to restricted documents.
May 2, 2026
PlatformEmerging Threats filters
Filter the Emerging Threats feed by CISA KEV, high CVSS, high EPSS, and CVEs that affect technologies found on your assets.
Apr 29, 2026
EngineTLS certificate detail and a larger Log Inspector
The TLS Monitor shows a grade, the certificate chain, key algorithm, forward secrecy and fingerprints for each certificate. Log Inspector accepts file uploads up to 10MB, recognises more than 80 log patterns and extracts indicators such as IP addresses, domains and file hashes.
Apr 21, 2026
EngineAPI Scans and OWASP API Top 10 on one page; manual pentest sessions saved
OWASP API Top 10 checks are an option on the API Scans page instead of a separate page. Manual pentest checklists are saved as sessions that you can resume, with results linked to findings.
Apr 19, 2026
UXPriority Fixes panel and inline actions on scan results
The DAST results page shows the five highest-severity failures in a "Priority Fixes" panel above the full check list. Every FAIL or WARN row shows a fix-time estimate, a severity dot, and "View Finding" and "Re-test" buttons. OWASP codes expand to full names (A05:2021 becomes "A05:2021 - Security Misconfiguration").
Apr 19, 2026
UXWhere to next: suggested steps after a scan
When a DAST scan completes, a "Where to next?" panel at the bottom of the results suggests next steps based on what was found, such as "Review All Findings", "Run SAST Code Scan" and "Attack Surface Inventory".
Apr 19, 2026
PlatformFindings: inline assignee and finding age
The findings table has an assignee dropdown on each row, with no modal. Each finding also shows how old it is (Today / 3d / 2w / 1mo).
Apr 19, 2026
ComplianceCWE to ISO 27001 mapping on findings
When a finding has a CWE ID, the matching ISO 27001 control is set automatically (for example CWE-89 maps to A.8.24 and CWE-287 to A.5.17). The mapping is applied when the finding is saved, with no manual entry.
Apr 19, 2026
PlatformSecurity Inbox: Recent Scan Alerts section
The Security Inbox has a "Recent Scan Alerts" section listing DAST scans from the last 7 days that had failures, with the target, the failure count and a link back to the results.
Apr 19, 2026
PlatformLegacy API routes retired: all traffic on versioned /api/v1/* endpoints
Unversioned /api/* routes have been removed. All API traffic uses the /api/v1/* namespace. Integrations that call the REST API should use the versioned URLs. The OpenAPI reference at /dashboard/integrations/api/reference lists the current endpoints.
Apr 19, 2026
UXMy Programme: security maturity benchmark
The Programme page includes a five-level security maturity panel (Level 1 Initial to Level 5 Optimised) based on your own data. Each level has stated criteria and the page shows which levels you have reached.
Apr 17, 2026
UXScan findings stay in place when you navigate
Findings from a scan that has just finished are kept when you go straight to the findings pages.
Apr 17, 2026
PlatformNIS2, ISO 27001, SOC 2, GDPR, PCI DSS and DORA framework pages
Six public framework pages, each showing how the framework's requirements map to Spoorder features. Linked from the Platform page.
Apr 17, 2026
PlatformComparison pages: Aikido, Snyk, Intruder
Three comparison pages with feature-by-feature tables: Spoorder next to Aikido, Snyk and Intruder, covering scan types, compliance mapping and pricing model.
Apr 17, 2026
IntegrationIntegrations page with setup links
A public integrations page lists the supported integrations by category (issue trackers, CI/CD, alerting, cloud, API), with setup links from each card into the dashboard.
Apr 10, 2026
PlatformHomepage updated: 15 engines, 8 frameworks, one platform
New homepage headline and call to action. Unlimited users on every paid plan, with no per-seat charges.
Apr 8, 2026
SecurityOut-of-band injection detection
DAST scans can detect blind injection vulnerabilities using out-of-band interaction tracking. Results appear in the scan view as findings, with no manual log checking.
Apr 5, 2026
PlatformBuilder, Pro, Scale, Enterprise: plan names and USD pricing
Simpler plan names. Builder ($69/mo), Pro ($199/mo), Scale ($449/mo), Enterprise (from $899/mo). All prices in USD. The Health Scan plan is free. No per-seat charges on any plan.
Apr 2, 2026
EngineCBOM: Cryptographic Bill of Materials
An inventory of the cryptographic assets found by your scans, with a post-quantum readiness score, evidence for NIS2 Art.21(2)(h) and change tracking between scans.
Mar 28, 2026
AIAI fix suggestions with monthly limits per plan
Review the AI-generated diff, apply the fix, and verify with a re-scan. 10 fixes a month on Builder, 100 on Pro, 500 on Scale and a custom limit on Enterprise. Not available on Free.
Mar 20, 2026
ComplianceDORA framework mapping on Enterprise
ICT risk register, incident classification and resilience testing evidence mapped to DORA requirements. Enterprise plan. The mapping shows coverage and gaps; it does not certify compliance.
Mar 15, 2026
EngineTLS Inspector: certificate metadata
Protocol version, cipher suite, signature algorithm, certificate chain and expiry tracking, shown in the Attack Surface TLS Monitor. Includes an evidence export for NIS2 Art.21(2)(h).
Mar 10, 2026
IntegrationSecurity gates: pass/fail policies for scans
Define pass/fail policies per severity and scan engine and evaluate a scan against them. Gates are evaluated from the dashboard by a Power User or above. See the 2 October 2026 entry for evaluating them from a pipeline.