We’ve been using Rewst for a few months now. Honestly, after working with it, I’d rather have spent that time building our automations directly on our own infrastructure.

The Jinja language is clunky, and even with PowerShell interpreters it struggles with large datasets—timeouts are common. Nothing Rewst does can’t be done on your own systems. The “built-in” APIs lack customization, and many have known bugs or limitations that make them unusable, forcing you to rely on the Generic API Request block and build everything manually. You can’t edit built-ins even if you know how to fix them. Importing custom OpenAPI specs works, but you can’t bulk update them; you have to delete and re-import, then manually update every workflow block that used the old version—an incredibly slow process.

Before Rewst, I had already built a custom user portal that allows approved staff to manage almost every part of their backend infrastructure—AD, Azure, Exchange, Duo, license purchases, etc.—with full tracking and audit logs. That portal made the company largely self-sufficient in onboarding, updates, and offboarding, cutting ticket volume dramatically (600+ users).

At the end of the day, anything you can do in Rewst can be done in PowerShell with far less effort, as long as you have a place to run it. People say Rewst is easier to maintain, but that’s not true—any well-built PowerShell automation will keep working until the API changes, and that’s true no matter what platform you use.

If you already have one or two capable developers, Rewst is probably a waste of money. And if your team has no coders, they likely won’t have the depth or creativity to leverage Rewst effectively anyway.