Deployment Options

# Deployment Options

> Choose a supported Conto hosting option and understand the customer responsibilities for each path.

- Human URL: https://conto.finance/docs/guides/deployment-models
- Raw Markdown: https://conto.finance/docs/guides/deployment-models.md
- Terminal view: https://conto.finance/ai/docs/guides/deployment-models

Documentation group: Guides

# Deployment Options

Choose a hosting option before you design authentication, wallet custody, webhooks, networking,
and operational ownership. Conto is provided as a hosted service by default. The source repository
is useful for development and evaluation, but it is not a packaged customer-operated production
distribution.

## Available Paths

| Option                           | When to choose it                                                    | Conto provides                                     | Your organization manages                                                                  |
| -------------------------------- | -------------------------------------------------------------------- | -------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| **Hosted Conto**                 | The default path for production and sandbox use                      | The Conto service and product updates              | Users, agent credentials, wallets, policies, approvals, webhook consumers, and contacts    |
| **Dedicated environment**        | Your requirements call for agreed isolation or network connectivity  | An environment and service scope agreed with Conto | Application access, payment controls, connectivity requirements, and customer integrations |
| **Local development**            | You are evaluating Conto or contributing to the project              | Public documentation and the source repository     | The complete local development environment and any test data                               |
| **Customer-operated production** | Your organization must operate the service in its own infrastructure | No turnkey package is currently offered            | Confirm this requirement with Conto before designing the integration                       |

If your architecture requires a dedicated environment, a particular region, private connectivity,
or customer-operated infrastructure, contact Conto before implementation. This avoids designing
against a hosting model that has not been agreed.

## Hosted Service Boundary

The hosted product exposes the dashboard, REST and OpenAPI endpoints, SDK and MCP integration
surfaces, webhooks, and sandbox workflows. Your organization retains control of:

- which people and agents receive credentials
- wallet custody choices and funding authorization
- policy values, approval routing, and counterparty configuration
- storage and rotation of API, SDK, webhook, and wallet secrets
- webhook availability, replay handling, and downstream accounting or ERP integration
- authorization to enable and use live funds

Treat Conto as an external service in your integration. Use request timeouts, idempotency keys,
bounded retries, request-ID logging, and reconciliation so an uncertain network response does not
cause a duplicate payment.

## Questions To Settle Before Integration

Record these decisions before moving beyond sandbox:

1. hosted or dedicated-environment path
2. region, network egress, and connectivity requirements
3. wallet custody and live-funding owner
4. secret storage and rotation owner
5. webhook destination, verification, replay, and recovery behavior
6. downstream accounting and reconciliation requirements
7. incident contacts and payment-stop authority

Continue with the [Production Readiness Checklist](https://conto.finance/guides/production-readiness) after the sandbox
integration is working.