Municipal data centres

Run AI sovereignly – every BSI and NIS2 requirement evidenced.

Ravi checks specialist applications and AI against BSI baseline protection, NIS2 and GDPR. He shows what is missing for secure operation – every requirement with a source.

Experience it live · free
The problem

Operations, oversight, sovereignty – the evidence is scattered.

System documentation, BSI baseline protection, NIS2 and GDPR: for every approval you pull it all together. And oversight or audit ask whether operations are demonstrably secure.

The question

You ask Ravi – in one sentence.

Instead of pulling everything together by hand, you simply ask. Ravi shows what is being checked – step by step, across all sources.

The evidenced answer

Every requirement comes with a source.

Every finding names the building block and the legal basis. Whatever is open, the agent clearly marks as an action.

Your next step

Ravi prepares – you approve.

The operational approval remains your decision. It only goes into production once you approve it.

Hello, I'm Ravi – your AI agent for secure operation. I keep an eye on BSI baseline protection, NIS2 and GDPR and let you know when something is missing.
I noticed three points about a new specialist application today:
Signals · today
CMDBSpecialist procedure: resident registration
c:node GraphNIS2 · applicability to be checked
c:node GraphBSI baseline protection · building block open
@Ravi, can we run this specialist application in our own data centre – BSI- and NIS2-compliant?
I'm checking all sources:
  • System documentation read
  • Protection needs determined per BSI baseline protection
  • NIS2 applicability (BSIG) assessed
  • GDPR requirements checked
  • Operating model compared against your requirements
Operation possible – with two open actions.
  • On-prem operation in your own data centre meets the sovereignty requirement
  • BSI building block for logging not yet implemented – address before approval
  • Document NIS2 reporting channels and name the responsible body
System documentationBSI IT baseline protectionNIS2 / BSIGGDPR Art. 32
I've prepared the next step:
Draft · action plan + approval template
Action plan for the open BSI building block and the NIS2 reporting channels, with a source for each requirement. Created for approval.
ApproveEditNothing goes out without approval

Example case with example data · legal bases real · not legal advice.

Sales booklet

Municipal data centres — the whole picture as a PDF.

Use cases, packages, rollout and the business case behind it — compact to take away and share.

Open booklet (PDF)
Get started

Your next step.

See c:node on your own case – or check where it runs and how it secures things.

See a demo on your case

Give c:node a small test run with a real question from your day-to-day – evidenced, step by step.

Book a demo →

See security

Where c:node runs, how you approve and what is evidenced – EU cloud Frankfurt or your own server.

See security →
FAQ

Frequently asked questions

Does c:node replace our security management?

No. c:node prepares the review – it connects system documentation with BSI baseline protection, NIS2 and GDPR and backs every requirement with a source. You do the approving.

Does c:node really run in our own data centre?

Yes. c:node runs on-prem up to air-gapped on your hardware – without internet, if that's what you want. Your data never leaves the building.

Where does the evidence come from?

From your system documentation and the c:node Graph – BSI IT baseline protection, NIS2/BSIG and GDPR. Every requirement carries its source.

Is it audit-proof for oversight and audit?

Yes. c:node produces an audit trail for every requirement, with source and legal basis, that you can show to oversight or audit.