---
title: Choose an integration
description: Decide between direct integrations, managed backends, and an explicit mixed-backend setup for your application.
---

The integration route owns authentication, limits, lifecycle mapping, and the network request. The platform remains the destination where an account or post exists.

| Route       | Use it when                                                                                                  | Application supplies                                                                                 |
| ----------- | ------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------- |
| Direct      | You want to call a platform API yourself and can satisfy its account, scope, review, and token requirements. | The platform application, authorization state, storage hooks where needed, and any upstream charges. |
| Zernio      | You want to use Zernio's supported connection and operation surface.                                         | A Zernio account and key, tenant mapping, and provider charges.                                      |
| Post for Me | You want to use Post for Me's supported connection and operation surface.                                    | A Post for Me account and key, tenant mapping, and provider charges.                                 |
| Mixed       | Different accounts deliberately use different configured backends.                                           | A named backend registry and an account-to-backend assignment known before dispatch.                 |

Mixed mode does not provide failover. An X failure cannot authorize a Bluesky post, and a managed-provider failure cannot move a connected account to another provider. Account authorizations and provider records do not migrate when application code changes adapters.

Before selecting a production route, consult its capability page for the exact operation, format, runtime, permissions, account eligibility, asynchronous behavior, cost ownership, and evidence level.

The [architecture diagrams](/concepts/architecture) show how route selection and per-target outcomes stay explicit.

For server integration shapes, see the [Node, Next.js, and Hono framework recipes](/getting-started/framework-recipes).