Sovereignty Guidelines

The Three Pillars of Enterprise Autonomy

We promote a standardized framework to help buyers assess sovereignty parameters. Listing publishers self-certify compliance with these core principles.

1. Self-Hosted (Air-Gapped)

The software must run entirely within your secure network boundaries. It requires no continuous internet connection to maintain basic functionalities and can operate in an offline, air-gapped environment.

Verifiable via: Dockerfile inspection Network analysis

2. Sovereign Backbone

Core engines must utilize transparent open-source foundations or standard frameworks. This ensures model weights are replaceable, vendor locks are broken, and the underlying logic is auditable.

Verifiable via: Model source audit Permissive licensing

3. Zero Data Retention

Absolutely no business metadata or raw inputs may be sent to third-party APIs. There is zero telemetry tracking, zero usage logging by the developer, and zero training on your corporate documents.

Verifiable via: Static code analysis GDPR/EUV compliance

Autonomy Self-Declaration Guidelines

01

Self-Audit Scan

Publishers inspect source code and configs to verify that no tracking webhooks, analytics, or outbound telemetry calls are embedded.

02

Sandboxed Check

Deploying the containerized module in an offline sandbox enables developers to self-test and verify network and storage isolation.

03

Open Backbone

Publishers ensure AI models run locally (e.g., GGUF, SafeTensors) and do not leak enterprise data to external SaaS API endpoints.

Portal & Sandbox

Publish Your Listing

Add your software module or project request to the registry. Run our self-assessment simulator to verify guidelines alignment.

List a B2B Software Module

Autonomy Self-Assessment Simulator

Enter your module's deployment configuration to simulate isolated offline execution. The sandbox runs a checklist check to help you verify network container isolation and document telemetry status.