Publishing on Batoi Exchange

Publish reviewed assets with lifecycle responsibility declared

Eligible publishers submit versioned manifests, provenance, permissions, data handling, compatibility, security evidence, documentation, support ownership, update and rollback plans, advisory handling, deprecation, and revocation terms.

Become a Partner Browse Exchange Assets

Batoi Exchange reviewed publication and support lifecycle

Eligibility

Publishing access depends on current eligibility, domain readiness, applicable review, and an accepted support and lifecycle commitment.

Exchange is

Certified Batoi Technology Partners

Certified Consulting or Solution Partners

Academy contributors (for models and blueprints)

Internal Batoi teams

Supported Asset Types

Extensions

Platform add-ons and utilities

Connectors

Integrations with external systems

Blueprints

Templates for projects, automation, or policies

Models

Structured logic for analytics, risk, or governance

UI Packs

Themes and layout components

Each asset must:

Declare its type clearly

Specify compatible Studios and Systems

Operate within defined scopes

Non-Negotiable Controls

Submitted assets must disclose enough information for the applicable trust, security, compatibility, permission, processing, and support review.

Mandatory requirements

Operate under platform identity and RBAC
Respect permission scopes and least-privilege principles
Emit audit events for significant actions
Avoid hard-coded secrets or credentials
Comply with applicable policy gates

Assets may not bypass platform security or policy enforcement.

Documentation Standards

Every published asset must include:

Clear description of purpose and scope
Installation, explicit capability binding, and configuration steps
Required permissions and dependencies
Compatibility notes
Support contact or escalation path

Documentation must:

be accurate and maintained
avoid marketing language
describe limitations explicitly

Compatibility and Lifecycle

Publishers must:

Declare compatible BCP and Studio versions
Follow semantic versioning
Maintain backward compatibility where feasible
Provide staged upgrade, migration, compatibility, and rollback guidance
Publish security advisories, deprecation schedules, and revocation instructions when required

BCP may:

flag deprecated assets
restrict incompatible versions
require updates for platform changes

Review and Approval

Certification status may be revoked if guidelines are violated.

Publishing follows a structured review:

Asset submission

Security and governance review

Compatibility validation

Documentation verification

Certification (if applicable)

Listing on Exchange

Publishers are responsible for:

Every published asset must include:

Asset correctness and updates
Security patches
User support (as declared)
Compatibility notes
Compliance with publishing policies

Batoi:

governs the platform
enforces Exchange standards
may suspend or remove assets if required

Licensing and Monetization

Assets may be:

Free
Subscription-based
Enterprise-licensed

Publishers must:

disclose pricing clearly
comply with Batoi commercial policies
avoid deceptive or conditional licensing

Enforcement

These actions protect platform trust and ecosystem integrity.

Batoi reserves the right to:

Suspend publishing privileges
Remove non-compliant assets
Require remediation
Notify affected customers

Assets may not bypass platform security or policy enforcement.

Quality Enables Scale

Exchange publishing is designed to encourage innovation while preserving control, security, and long-term trust.

Become a Partner View Exchange Assets Contact Exchange Team

Frequently asked questions

Who can publish assets on Batoi Exchange?

Certified Batoi partners, Academy contributors, and internal Batoi teams may publish assets after meeting governance and documentation requirements.

Are Exchange assets reviewed before publication?

Assets submitted to the controlled publication path require the applicable security, governance, compatibility, provenance, permission, documentation, support, and lifecycle reviews before listing. The resulting trust status and limitations should remain visible.