Holden - Hello - If I'm building some demos for...
Hello - If I'm building some demos for several companies, and they are very similar, should I just copy the workflow I use, within the same project? Or, should I create a new project for each company? Related question - is pricing impacted by number of projects you have or just number of workflows? How about concurrent executions, does it matter if they are conncurrent workflows within the same project or in 2 different projects? Thanks!
Solution:
Jump to solution
Hello @Holden, If the companies also require the access for your backend (BuildShip), contains multiple workflows and would be deploying it on prod on their app, then I would recommend making separate project for each company based on their requirements, as you'll be also able to invite them to collaborate to your BuildShip project.
If the backend will only be accessed by you and solely for demo purposes, then keeping it in the same project within different folders will be a good start.
The pricing of BuildShip is on per-project bases. You can refer to the FAQs - https://buildship.com/pricing....
1 Reply
Solution
Hello @Holden, If the companies also require the access for your backend (BuildShip), contains multiple workflows and would be deploying it on prod on their app, then I would recommend making separate project for each company based on their requirements, as you'll be also able to invite them to collaborate to your BuildShip project.
If the backend will only be accessed by you and solely for demo purposes, then keeping it in the same project within different folders will be a good start.
The pricing of BuildShip is on per-project bases. You can refer to the FAQs - https://buildship.com/pricing.