Seats are for any user of the UI and they aren't bound to a person, so you can reassign them as necessary.
For larger teams we do buckets of seats with price reductions per-seat as the team size goes up.
We don't rate limit deploys - as that would make you less agile, we don't charge based on resources because that penalizes teams with stable infrastructure.
We know ops budgets can be tight, we're ops engineers, so we try our best to make the pricing work well for those budgets.
Massdriver isn’t aimed at pre-funded startups. Early-stage teams are often better off with a PaaS or setting things up manually until ops challenges become a bottleneck.
Our pricing (5-seat minimum) is intentional to dissuade smaller teams. The real value kicks in when teams need self-service. Ops teams build the modules (not us), and Massdriver acts as the interface. Developers diagram what they need, and Massdriver provisions using the ops team’s standards. This keeps developers focused on building while giving ops visibility and control over what’s deployed.
So does mass driver become a single source of truth for all information about my companies entire cloud or does it only maintain a track of what's been deployed through it.
I have a friend whos a manager at a large e-commerce company who's teams entire responsibility is to oversee all matters regarding their private and public cloud usage. They also manage and maintain services for internal use.
I would love to recommend you guys to them because managing deployments from over a dozen teams located around the world is hell for them. However they have an extensive private cloud setup, would your solution be as applicable to them as it is to companies running on public clouds?
It is a single source of truth, but only what is managed through the platform.
Private cloud isn't the best experience right now, its possible, but it requires our platform being able to 'get inside' so we either need a control plane exposed to us or a VPN connection in.
Self-hosted is our #1 requested feature, so we are cranking away at it. Its in alpha, and we're looking for testers/feedback. Would love an intro!
When you get self-hosted up and running, you may also want to consider open sourcing the private cloud portion as well. Think of it more as a marketing thing. Many companies <5 people tend to either go all-in on the cloud, or their own servers if bootstrapping. For teams on the cloud, they don't need your product, yet. For teams who are running their own private clouds, they do. Eventually, they'll grow into the cloud and bam, they start paying you.
How do you intend to get any adoption with pricing like that? I’m certainly not going to drop several hundred dollars to see if your product is better than any of the freely available IaC tools.
Not trying to critizice, just don’t understand how this works. I’ve got my company to pay for Pulumi after several years of usage, but I needed to be able to use it to get that far.
Trust em or not … had that happen to someone else using Cursor a few weeks back. I ran a prompt for refactoring a function and all of a sudden it started dumping someone else’s directory structure and file contents into my text file. Like hundreds of files. Not exactly sure what happened but I immediately uninstalled Cursor.
For larger teams we do buckets of seats with price reductions per-seat as the team size goes up.
We don't rate limit deploys - as that would make you less agile, we don't charge based on resources because that penalizes teams with stable infrastructure.
We know ops budgets can be tight, we're ops engineers, so we try our best to make the pricing work well for those budgets.