We decided to shift our billing method to pay as you go pricing in the cloud and tasks became cheaper.
The Story
We’ve been all ears to your feedback, and we’ve noticed that many of the users aren’t happy with how the industry typically bills for tasks. Figuring out the fair price for tasks has been a bit of a puzzle.
But our mission to democratize automation and make it accessible to everyone even if that means we lose short term revenue but we want everyone to adopt the tool and stay there
The Problem
Packages with fixed prices don’t adjust for sudden increases or one-time big tasks. We’ve seen folks switching between plans every few months because of this.
It takes effort to calculate and pay for your usage upfront, but sometimes it’s hard to know which package is the best fit.
Pricing gets complicated, especially when it’s combined with plans that have specific features locked behind them.
As your workflows expand, you might realize that your automation platform becomes too pricey, leading you to switch to less convenient options like coding.
we’ve listened.
You’re in Control!
With our new model, you can:
Pay as you go: It’s easy! Just $1 for every 1,000 tasks.
Set spending limits: Avoid surprises by setting a maximum on your task usage.
If you’re on a plan with committed tasks, you can activate the pay-as-you-go option alongside your current plan by heading to the plan page and adding your payment details.
@Eduardo Yes, that means you will pay after the 50k, and the sync time has nothing to do with the pay-as-you-go model, so it will stay the same for everything
I’ve just signed up for the PAYG pricing and would like to understand how a task in measured, as I haven’t found anything relevant in the documentation.
I did a run of a flow with 24 steps and by the end of the run, my task usage had increased by 1,681 tasks. That’s an average of about 70 tasks/step.
I assume that different steps in the flow use up different amounts of “tasks”, but I can’t find any details on this. Can someone point me to the relevant documentation, or explain the relationship between steps in a flow and task consumption?
Issue were found in testing mode, It should count 24 tasks but there was an issue with duplicate counting only at “Test Mode”, the tasks will be recalculated and fixed soon again by our usage and billing system tonight and it will automatically reflect on billing and usage.
Thank you so much for reporting the issue, and sorry again for the inconvenience caused.
Thank you for the update. The existence of a bug makes sense to me as an explanation of what I was seeing. I had assumed before signing up that it would be one task per step, but when I saw that my consumption was different, I thought that maybe there was some kind of formula for certain steps using up more tasks that I had missed in the documentation!
I’ve just checked my usage and can see that the number of tasks is now in line with the number of runs that I have had. Big thanks to you and the team for sorting this out so quickly.
For those with smaller automation needs under ~30,000 tasks/month, Make.com is now a better deal and a more mature platform. The pay-as-you-go model was also a great entry point for learning and scaling automation for those just starting out, who’d initially balk at a $25/month subscription.
I agree that if you plan, from the beginning, to scale up then it makes sense. It’s obviously a better deal for an established, high-volume automator shopping around. That seems to be what the industry is targetting right now. On the other hand, I think $25/month is a barrier for smaller businesses customers and individuals interested in personal productivity, who may just want to try automating a few things and learning the ropes. If not for AP’s pay-as-you-go I would’ve never taken step 1.
Make is not leaps and bounds ahead of AP, but a lot of the APIs are more built out there than at AP. There are also more connectors in general. Several APIs I’ve used via HTTP on AP are built into Make, for instance. Nothing that is insurmountable, and there are several things that AP already does better. But for someone starting out, the more established brand can carry more weight, especially when there’s a budget pricing plan. And for the people I have in mind, self hosting an open source application is probably completely out of the question. I think the established power of Zapier is a good example here: they are much more expensive than everyone else, but remain the most popular platform.
Thanks for spending the time to write this. We’re still learning and developing our new pricing plans.
The team will be happy to support your automation journey as a supporter. Please screenshot this comment, and share how you use Activepieces today and what are the limitations in your journey and they’ll definitely help you, at support@activepieces.com
We’re also ramping up our pieces through the open source community bounty program, we’re investing heavily there and we expect to reach 1,000 pieces by the end of the year.
because for small business, it doesn’t make sense. We don’t need 25k tasks. perhaps we only need 2-3k. It’s helpful to have the PAYG. As the company/business grows, then their tasks grow, eventually they would need to upgrade.
The Story
The Problem
You’re in Control!
In most of cases we have seen so far the new plans are cheaper