> ## Documentation Index > Fetch the complete documentation index at: https://docs.didit.me/llms.txt > Use this file to discover all available pages before exploring further. # Marketplace > Choose which engine runs each workflow feature: Didit's own, or a third-party provider you connect from the Marketplace, with automatic fallback to Didit. The **Marketplace** lets you connect third-party identity verification providers to your organization and choose, feature by feature, which engine actually runs the check: Didit's own engine, or a provider you connect yourself. *** ## Choosing an engine per feature Every feature node's first configuration tab — in both **Simple** and **Advanced** workflow mode — starts with a **Verification engine** control. It shows the engine currently running that check and, next to it, how many providers are available for that feature. Opening the control lists every provider for that feature with an explicit status: | Status | Meaning | | ----------- | -------------------------------------------------------------------------------------------------------------------------------------- | | **Active** | This is the engine currently selected for the feature. | | **Switch** | A provider you've already connected. Select it to make it the active engine for this feature. | | **Connect** | A provider you have not connected yet. Selecting it opens the setup dialog so you can connect it without leaving the workflow builder. | Features that only Didit's own engine supports show that engine with a "no other providers" note and a direct link into the Marketplace, so the control stays consistent across every feature even where there is nothing to switch to. ## Automatic fallback to Didit Once you select a connected third-party engine for a feature, a **Fall back to Didit if my provider fails** switch appears for that feature: * **On** (default): if your provider is unavailable, Didit's own engine runs automatically for that step, so the verification never fails outright. * **Off**: if your provider is unavailable, the step fails instead of silently running on Didit. ## Configuring engine selection through the API Engine selection and fallback are not part of the [workflow feature config reference](/management-api/workflows/feature-configs) — the Management API accepts them as `provider_key` and `fallback_to_native` on the feature's `config` object, but they are managed through this Marketplace UI rather than being documented per-feature fields: | Field | Type | Description | | -------------------- | ------- | ------------------------------------------------------------------------------------------------------------- | | `provider_key` | string | The key of the connected provider to run this feature. Omit it, or leave it unset, to use Didit's own engine. | | `fallback_to_native` | boolean | Whether to fall back to Didit's own engine if the selected provider is unavailable. Defaults to `true`. | *** Build the workflow that each feature's engine selection applies to. The full config reference for every workflow feature.