Is there a cloud version?
No, deliberately. Your findings describe exactly where you are weakest. PYXA runs on your own Docker Compose stack, one instance per company, with no multi-tenant SaaS and no phone-home, in every edition.
What does the Community edition leave out?
Single sign-on and LDAP; the Defender, CrowdStrike, Inspector, Wiz, Snyk, GitHub, GitLab, ServiceNow, attack-surface and BloodHound connectors; GLPI, TheHive and ServiceNow tickets and webhooks; the CISO board PDF and PCI DSS evidence pack; the compliance self-assessments; and AI beyond remediation guidance. Auto-triage is limited to 3 rules. Everything that closes the loop, from scanner to verified fix, is in it.
Do we need consulting to make it work?
No. Professional and Enterprise include a two-day install with your team, which ends with the scanners connected and the first campaign open. Community setup walks an empty install to a working one. PYXA Consulting is a separate contract for organisations that want the programme itself built or audited.
What does the compliance assessment certify?
Nothing on its own. It computes framework controls from your data, one of NIS2, TISAX or PCI DSS v4.0 in Professional and all seven in Enterprise, and marks what it cannot answer instead of passing it. It is a self-assessment aid, not a certified audit, and evidence starts on the day PYXA is installed.
What happens if PYXA stops trading?
The data never left your server, so nothing is lost, and the Community edition stays available under AGPL-3.0. Enterprise includes source-code escrow.