# Going live

## Preparing to go live

- Before you go live with your initial version, revisit the decisions from the [Introduction](https://developers.enode.com/docs/integration-guide/introduction) and consider your answers about cohorts and devices you’ll enable
- If you haven’t done so already, you should [request access](https://enode.com/contact) to a production client that will enable you to connect real devices
- Before launching with “real” users, we strongly recommend following our [testing best practices](https://developers.enode.com/docs/integration-guide/testing) and test in live mode with a very small handful of people and devices first

Production access requests: Please note that Enode does not support personal development projects in the production environment. Access requests should only be submitted for production-ready use cases.

## Supporting your users

- Use experience gained from small-scale live testing and our guide on [sad paths](https://developers.enode.com/docs/integration-guide/sad-paths-and-errors) for common scenarios that you may want to prepare your support and operations team for.
- Your users should rely on your support teams for frontline support. Consider creating public FAQs or internal support wikis before going live
- If you need to escalate any issues, we’re here to help. We encourage your engineering or product teams to contact us through our [support page](https://developers.enode.com/support).

## Managing vendors and growth

- As you learn from your experience with launching and begin to receive feedback about your initial version, you should gradually release support for more devices and categories
- Refer to our [brands overview](https://developers.enode.com/brands) to help make the best decisions on which devices you should support next