IMO: For something B2B like this, plans are a way to segment your customers. Your solution might not be worth much to someone's side project, while it might be replacing an entire employee's worth of work for a larger company, saving them thousands of dollars a month.
You might want your basic plan to do everything a solo developer or hobbyist needs, your middle plan to do everything a small shop or agency needs, and your top plan to do everything a household brand needs for example. Then price accordingly to the greater value and ability to pay each group has.
Come up with the plans and price them according to that mindset. If the main thing that differentiates your customers is the number of users, or number of servers they run, or how many API calls they process, or what level of support they need... that's the metric you want to find and use to set your pricing. Not necessarily the technical parameters of your product. Maybe that "wiring into a CI" is the only thing that differentiates your customers, and you only need two plans.
Decide on something and put it up. You can always change your pricing later (painlessly if you grandfather existing accounts) as you learn more from actual customers.
