Home Product & Regulatory Updates v1.1.0 — 2026-06-03 · Help Center, Captain Nex, regulatory baselines

v1.1.0 — 2026-06-03 · Help Center, Captain Nex, regulatory baselines

Last updated on Jun 03, 2026

TL;DR

NexCyber v1.1.0 ships the public Help Center, the Captain Nex AI copilot, and the baseline coverage for the five regulations on which NexCyber operates (CRA, NIS2, AI Act, DORA, RED Cyber). It also strengthens the operational support layer (SLA policies, business hours, escalation matrix) and ships a formal vulnerability disclosure policy under RFC 9116.

What changed

Help Center — public surface

  • Skin of docs.nexcyber.eu reworked: clear navigation, mobile-ready layout, consistent terminology (NexCyber as the single product name).
  • 50 articles published across Getting Started, Solution Guides, regulatory basics (CRA · NIS2 · AI Act · DORA · RED Cyber), Billing & Plans, and FAQ — covering the platform end-to-end at bootstrap depth. Customers portal mirrors a complementary set of 25 articles for logged-in users.
  • Diátaxis structure: every article follows one of tutorial · how-to · reference · explanation. The header tells you which type you are reading; the "Next step" footer points you to the right follow-up.
  • What NexCyber does NOT replace — a dedicated article makes the boundary with legal advice, notified-body certification, and independent audit explicit. Every regulation page repeats the boundary.

Captain Nex — AI copilot in the support widget

  • Captain Nex is live in the support widget on the docs Help Center.
  • Language stickiness: Captain replies in the language of your first message and stays in it for the conversation (EN, FR, DE, ES, IT).
  • Two modes: when you are logged in, Captain operates as a product coach (onboarding, quick-start, scope, assessment, evidence, report). Anonymous visitors see Captain in sales-aware concierge mode (value, plans, modules, regulatory coverage).
  • Hand-off: Captain hands off to a human for sensitive regulatory questions, billing disputes, security events, or any case where it is not confident.
  • No legal opinion: Captain explains how NexCyber works, never interprets the law for a specific case.

Operational support layer

  • Five SLA policies active (Standard · Guided · Priority · Enterprise Ops · Premium Success) mapped to plans.
  • Business hours (Mon–Fri 9–19 CET, Europe/Paris) enabled on every inbox so SLA timers reflect real working time.
  • Functional inboxes added — Sales, Compliance, Billing, Security — alongside the existing regional support email inboxes. Routing to the right team is automatic.
  • Escalation runbook L1 → L6 is documented and applied (Captain Nex → human support → product/engineering → regulatory expert → security → executive). Internal-only but the customer-facing effect is that your conversations always land at the right human.

Regulatory baselines audited

  • CRA, NIS2, AI Act, DORA, RED Cyber — baseline coverage is in place. Each regulation has a Help Center page, an assessment scaffold, and clear guidance on what evidence to collect.
  • The baseline is the floor, not the ceiling. Deeper guides (per Article 21 NIS2 measure, per AI Act Annex III area, per DORA pillar) are scheduled in the next release trains.

Vulnerability disclosure policy (RFC 9116)

  • security.txt is published at the canonical paths:
    • https://support.nexcyber.eu/.well-known/security.txt
    • https://docs.nexcyber.eu/.well-known/security.txt
  • Contact: security@nexcyber.eu. Preferred languages: EN, FR. Policy article published in the FAQ section.
  • We commit to acknowledge within 2 business days and to provide a triage update within 5 business days.

Why it matters

A regulated buyer asks four questions early: what does this product cover · how does it work · what does it guarantee · how do I trust the team. This release answers each one in a way you can read, share, and bookmark.

  • Coverage = Help Center categories + regulation pages.
  • How it works = the four-step flow (Scope → Assessment → Evidence → Report / MRCC).
  • Guarantees = the SLA policy + the What NexCyber does NOT replace boundary.
  • Trust = security.txt + the Data security and confidentiality page + the Responsible vulnerability disclosure page.

Action required

Nothing mandatory. If you want to take advantage of the release:

  • Open the Help Center and use it as your in-house knowledge base for the team.
  • Subscribe to the Product & Regulatory Updates category to be notified of subsequent release notes.
  • Encourage your security team to review the security.txt policy.

If you are an existing customer with an open question that the new content does not yet answer, open the widget and Captain Nex will help.

Effective date

2026-06-03, 09:00 CET (Europe/Paris).

Affected modules

  • Help Center (public + customers portal).
  • Captain Nex (AI copilot in the support widget).
  • Support operations (SLA, escalation, business hours, functional inboxes).

Affected regulations

CRA · NIS2 · AI Act · DORA · RED Cyber — baseline coverage activated.

Plans impacted

All plans. The support level and response targets remain plan-specific (see Support plans and response targets).

Rollback

The release is additive. No data migration. If a specific article or feature creates a problem, we can disable it surgically without rolling the full release back.

References

  • Release notes and regulatory updates — what to expect — process article.
  • What is NexCyber? — product overview.
  • Support plans and response targets — plan / SLA mapping.
  • Responsible vulnerability disclosure — security reporting.
  • security.txt — vulnerability disclosure machine-readable policy.

Next step

Open Subscribe to updates in your workspace notification settings, or just drop our RSS feed in your reader.