Korynthe helps small businesses understand posture, prioritize current risks, track readiness, and move faster with evidence-backed guidance. It is not positioned as a 24/7 SOC, a full audit substitute, or an all-of-security platform.
Live and marketable today with real routes, evidence-backed behavior, and current UI/API support.
Live, but intentionally scoped. Use this for Azure depth, narrow remediation coverage, or other capability areas where boundaries matter.
Use these labels for earlier-stage or not-yet-delivered capabilities so buyers know what is emerging versus what is production-ready.
This is the baseline entry point into Korynthe. It turns your public-facing domain, email, SSL, and web posture into a clear external security picture.
Run a free, verified business-domain scan for email authentication, SSL/TLS, security headers, and exposed infrastructure.
Why it matters
This gives SMBs a practical first security baseline without pretending to be an internal audit.
Included in: Korynthe Insight and above
Paid tiers add broader route sampling, richer DNS and DMARC parsing, live email-auth validation, and stronger technology fingerprinting.
Why it matters
The paid path improves context and change tracking instead of just repeating the same one-time scan.
Included in: Korynthe Core and above
Re-check external posture on a schedule and preserve scan history so teams can track improvement and catch regressions.
Why it matters
Security programs need trend visibility, not just one screenshot from a point in time.
Included in: Korynthe Control and above
Korynthe is strongest when public posture data is paired with connected Microsoft 365 or Azure evidence. These connected paths are intentionally scoped and should not be marketed as universal deep-platform coverage.
Review Entra, Exchange, SharePoint, and selected Purview-adjacent controls for identity, sharing, email, and audit posture.
Why it matters
For many SMBs, Microsoft 365 is the most sensitive environment they run. This is one of the most credible product areas today.
Included in: Korynthe Control and above
Connect Azure for a read-only baseline posture review of supported resources, current control gaps, and workload-first cloud risk context.
Why it matters
This gives cloud visibility without claiming to be a full enterprise cloud governance suite.
Included in: Korynthe Vanguard
Google Workspace support exists, but the current path is lighter and less mature than Microsoft 365.
Why it matters
Buyers should expect meaningful Microsoft depth first and treat Google as an earlier-stage path.
Included in: Korynthe Control and above
Korynthe’s category strength is not raw scanning alone. It is using that evidence to drive prioritized risks, framework readiness, and reports leadership can use.
See medium-and-above risks surfaced from current scans instead of maintaining a heavy manual register by hand.
Why it matters
Small teams need a current risk picture tied to live evidence, not another spreadsheet to babysit.
Included in: Korynthe Command and above
Map scan evidence into readiness workflows for frameworks such as NIST CSF, SOC 2, and HIPAA while keeping evidence and reports in one place.
Why it matters
This helps SMBs prepare for customer and compliance pressure without presenting Korynthe as a substitute for a full external audit.
Included in: Korynthe Command and above
Generate reports, executive summaries, and branded outputs that explain posture, major gaps, and next-step priorities clearly.
Why it matters
Security tools often fail when they cannot explain the work to leadership or customers.
Included in: Korynthe Control and above
The AI layer is there to reduce interpretation overhead. The automation layer is there to help teams act faster where the product has enough evidence and safety to do so responsibly.
Use AI to draft policies, explain technical findings in plain English, and generate practical improvement roadmaps from actual posture data.
Why it matters
The AI story is credible when it shortens the path from scan to understanding to action.
Included in: Korynthe Control and above
Selected Microsoft 365 changes can be executed through warning-gated remediation flows with explicit change explanations, separate per-admin remediation consent, and limited rollback for safer cases.
Why it matters
This closes the gap between knowing and fixing without pretending that every control is universally auto-remediable.
Included in: Korynthe Command and above
Wider rollback-capable remediation across more Microsoft 365 and cloud controls is still an expansion area, not the current product center of gravity.
Why it matters
Buyers should understand the current remediation scope before expecting one-click changes everywhere.
Included in: Future platform expansion
The cleanest buying path is still the same: start with external posture visibility, then connect Microsoft 365 or Azure when you need a fuller picture.