Customer Deployment

It’s as simple and fast as a few hours to give your team a self-service deployment capability into any AWS or GCP account, with maintenance and monitoring options built right in. We’ve called this various things: “customer deployments,” “on-prem,” and “own cloud.” So if those terms are more familiar, this page might still be useful for you. Please get in touch if you've got any questions on how this can work for your team.

Compared to other solutions, Coherence is appealing because:

  • Coherence is easy to set up and is simple to use
  • Coherence supports "day 2" tasks such as monitoring and maintainence
  • Coherence does not require a large deployment footprint such as a kubernetes cluster in the target account. You can rely on simple, fully-managed services that are easy to maintain over time
  • Coherence can also support your team with internal developer experience and productivity use cases such as Preview Environments or Velocity monitoring

Why do software companies’ customers want their own instance or to host in their own cloud account?

  • Data ownership and compliance requirements
  • Scalability concerns when sharing an instance
  • Depending on the SaaS, ability to customize some parts of it
  • Ability to control the rate of change, to reduce bugs and to improve ability to train employees on the specific version deployed
  • Integration into other “on-prem” systems

Coherence Support for Customer Deployments

Coherence can enable your team to spin up new customer environments in just a few minutes. Just as important, it also makes it easy to monitor, maintain, and support those deployments going forward. Here's how it works.

Set up your first Coherence application

Read our migration guide for more information on the set up process.

Test your application

You'll know how to do this better than we can, but make sure your app works end-to-end, including things like databases and logging.

Set up a customer environment

With your existing coherence.yml file in place, you'll be able to install the same configuration into your customer's AWS or GCP account by onboarding it again as another Coherence application. You might need their team's support to add the required IAM role.

This will provision a staging/pre-production environment for them. Alternatviely, you can set this up in your own account if they don't require access to it.

You'll then be able to add their production environment by adding the required IAM role to their account and promoting your first build into it. You'll be able to update their deployment with just a click in the future when they're ready for the new version, as well. Coherence will make sure the infrastrucuture stays up to date as the application remains deployed.

Manage and monitor the environment

You'll be able to use tools in your cloud, or use or integrations with products like DataDog, to easily keep an eye on the deployment. You'll also get access to the toolbox if you need to take action in an environment.

Can I develop locally?