---
title: "Comment by Adam Heathcote on \"How I Host a Separate JobOps Instance for Every User\" | Hashnode"
description: "A good way to automate some of this while still keeping manual control might be ChatOps. You could have a call back from Stripe that starts something like Hubot"
url: "https://hashnode.com/posts/hosting-jobops-cloud/69d29af340c9cabf441717a7/comment/69f0486a6ad9c5aa3b5d4c5f"
---

[Discussion](https://hashnode.com/posts/hosting-jobops-cloud/69d29af340c9cabf441717a7)

Comment [How I Host a Separate JobOps Instance for Every User](https://hashnode.com/posts/hosting-jobops-cloud/69d29af340c9cabf441717a7)

[Adam Heathcote](https://hashnode.com/@feisar)

[Apr 28](https://hashnode.com/posts/hosting-jobops-cloud/69d29af340c9cabf441717a7/comment/69f0486a6ad9c5aa3b5d4c5f)

A good way to automate some of this while still keeping manual control might be ChatOps. You could have a call back from Stripe that starts something like Hubot or Errbot which sends a message into your chat app (Discord, Slack, etc...) with the details. You can then reply to it with a command like "/provision subdomain" and it can then go off and do the work.

You are still able to review everything but it simplifies the workflow.

[Shaheer Sarfaraz](https://hashnode.com/@DaKheera47)

[Apr 28](https://hashnode.com/posts/hosting-jobops-cloud/69d29af340c9cabf441717a7/comment/69f0486a6ad9c5aa3b5d4c5f#reply-69f069136ad9c5aa3b8103ad)

Yeah actually. Using discord is an interesting idea because it means I can provision a user from anywhere, and not have to be on my laptop
