> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# Go-Live for ISVs

When you are ready to launch your integration in our production environment, you will need to promote your application’s integration key from your Docusign developer (demo) account to a production Docusign account using the [go-live](/platform/go-live) process.

**Note:** If you have enrolled in the Docusign ISV Referral [Partner program](https://partners.docusign.com/s/join-now) and have completed the application review process, Docusign will give your company a complimentary ISV partner production account that you can use to promote and manage your integration key(s) in production.

The Docusign go-live process has two steps:

1. An automated technical check of your application’s use of the Docusign APIs.
2. Confirmation of the decision to go-live and selection of a production Docusign account into which to promote the key.

* The production integration key has the same key value as the demo platform version, but they are two separate integration keys.
* The production integration key can be used by any Docusign production account of any type, by any user, on any production system (North America, Europe, etc.) to which your application provides access.
* The production integration key is managed by exactly one production account. This account can be a paid production account your company has, or a free ISV partner account. ISV partner accounts are provided to Docusign ISV Referral Partner program members who have successfully completed our application review process.

**Pro tip:** Create an email distribution list (email alias) or mailbox within your company such as [docusign@company_name.com](mailto:docusign@company_name.com) and use that email address for your primary developer account and the production account that will manage your integration keys. This will help prevent loss of access to the accounts when key employees leave your company. The password for the Docusign account must be updated if an employee on the team leaves your company.

After the go-live process has completed, the demo (developer account) version of the integration key is still available and should be used for weekly regression testing to ensure that API changes from Docusign will not affect your application. All integration demos and training (both customer and internal) should use a Docusign demo (developer) account and not the ISV partner production account. The complimentary ISV partner production account is provided for the partner to manage their production integration keys, not to send envelopes in production.

Since it can take several weeks to join the [partner program](https://partners.docusign.com/s/join-now), ISVs should apply to the program as early as possible.

## Learn more

* See [After Go-Live](/platform/go-live/after-go-live) for steps to confirm that your application is correctly configured for production.
* See [Docusign API endpoint base paths](/platform/api-endpoint-base-paths) for a list of production base URIs.