Configuration

Voyant is configured through the managed dashboard and its documented integration contracts. You do not assemble a deployment, select infrastructure providers, or maintain a runtime manifest.

​

What your organization configures

Configuration belongs to the business or integration surface that owns it. Voyant validates these settings at the owning API boundary and applies them to the managed service. Sensitive values are submitted through the relevant credential or connection flow rather than committed to a project file.

​

What Voyant manages

Voyant owns the complete runtime profile for every managed deployment. That profile includes:

• the product modules and migrations in the release;
• database, cache, storage, jobs, search, messaging, and runtime providers;
• the immutable runtime image and its release capabilities;
• regional placement, health checks, upgrades, and rollback;
• the platform-owned snapshot used to start the tenant runtime.

These are operational implementation details, not customer configuration. A tenant cannot inject a plugin, replace an infrastructure adapter, omit a standard module, or provide a voyant.config.ts file to alter the managed runtime graph.

​

Apps and admin extensions

An app extends Voyant through the public app contract. Its reviewed manifest declares its identity, permissions, compatibility, and extension surfaces. After installation, the organization grants the requested permissions and configures only the settings that the app exposes. Admin pages, widgets, and actions run through named extension points. They do not replace the dashboard shell or modify the tenant runtime profile. See Admin UI extensions and App compatibility for the supported contract.

​

Supplier and service connections

Supplier connectivity is configured as a managed Connect connection. The connection identifies the admitted adapter, stores its credentials through the managed credential flow, and exposes only the capabilities supported by that adapter. See Connect concepts and the provider SDK. Other service integrations follow the same boundary: choose an available managed integration, grant its documented permissions, and configure its customer-visible settings. The backing infrastructure remains owned and operated by Voyant.

​

Changes and releases

Business configuration changes take effect through their owning managed API. Changes that require new product code ship as an immutable Voyant release and are promoted through canary and stable channels by Voyant. Customers do not upgrade packages, run platform migrations, or reconcile generated runtime artifacts. For automated configuration and integrations, use the documented API, SDK, and webhook contracts. Those contracts remain stable even when Voyant changes its internal runtime composition.

​

Next steps