The new Rewst platform is now available for new customers. It's the secure automation platform your whole stack runs on. This post walks through where to start.
Every MSP has a list of automations it decided not to build, because the build would take longer than the problem justified. AI has made writing automations easier, so those time-consuming builds are an option again. But while writing them is easier, running your whole business on them hasn’t. A generated workflow still needs somewhere to execute, retries when an API times out, credentials scoped to the right client, sequencing when automations depend on each other, an alert when it fails silently at 3 a.m., and a record of what ran. Build all of that yourself and you're running a part-time software company. Rewst is the platform that keeps work running.
The new Rewst changes who can solve these problems. Anyone who understands the work can ask a question, take action across their connected tools, and turn tasks that repeat into automation, with the controls needed to run it securely across clients.
Not every task needs a workflow. Some asks never need a build at all.
Ask what's open past SLA or which licenses sat unused last quarter, and one answer comes back even when the data lives in three systems. A single request reaches whichever connected tools hold the answer, and those asks are scoped and logged too.
Your techs may already be using AI tools on their own, sometimes with client credentials. Rewst gives that work a governed place to happen instead. Ask the Rewst Agent directly or work from the AI assistant your team already uses through the Rewst MCP Server.
The clearest lesson from our Early Access testing: don’t start with the biggest automation you can imagine. Start simple, and build a foundation you can continue to expand. If you’re struggling with where to start, you’re not alone. In Rewst's 2026 industry survey, 48% of MSPs said not knowing what to automate was one of their biggest barriers.
The new Rewst can help. Ask the Agent to analyze your own tickets and recommend which automations would free up the most time. Or ask for ideas based on the tools you’ve connected.
Then pick one. The goal isn’t to build everything right away. It’s to get the first useful thing running and build from there.
Describe the problem in plain English, whether that's ticket triage or the access requests that land every week.
The Rewst Agent generates a complete workflow using your connected integrations, handling the code, data transformations, and conditional logic. A few minutes of prompting is enough to start, and the Agent keeps working while you clear the queue or focus elsewhere.
What it builds lands on the same canvas you'd use by hand. See every action, refine it, and decide what needs a second pair of eyes before it runs. An engineer can take over at any point when more control is needed.
The Agent can't create, update, or publish a workflow or form without explicit approval, and it must ask again before publishing.
This widens the pool of people who can contribute to automation. The vCIO who understands what matters in a QBR can build their perfect QBR scorecard. The service manager who understands ticket triage can describe what needs to happen in their unique system, rather than forcing a poor fit with a limited tool. Your senior team spends less time starting from scratch and more time refining the work that actually needs their expertise.
Each client is kept apart, and you reach all of them from one login. Credentials stay scoped to the client they belong to, and role- and resource-based access lets you decide who can work with each client and connected system. Publishing is its own permission, so only the people you choose can put work live.
Build the process once and adapt it per client, instead of maintaining a separate build for every client. Rewst keeps the actions that ran in one place per client, so you can tell what ran and who put it live.
Once you’re automating your own delivery, ask what should move outside your MSP.
With the new Rewst, the forms, portals, dashboards, and reports come from the same platform that runs the work, with no second (or third, or fourth, or fifth...) license needed.
Start small. Give a client a branded form that runs the workflow behind it, under the permissions you set, so a request doesn’t become a ticket. Or give them a report they'll actually read. Then repeat the offering across your client base, adapting it for each client rather than rebuilding it from scratch.
Automate your own delivery first. Then the forms, dashboards, and reports clients see become a service you can price, not a markup on someone else's tool.
"We wanted a strategic business review that shows clients what we've saved them, not just ticket counts. I took my original prompt, gave the new Rewst our logo and color codes, and said, build me something. It worked out of the gate. I got 95% of the way there in one prompt."
Jim-Barry Behar, Founder and President, Relentless Solutions
The backlog of things that weren’t worth automating has changed. So has the number of people who can do something about it.
You don’t need to start by rebuilding how your MSP operates. Connect your tools. Ask a question. Find something that repeats. Describe what should happen. Review what the Agent builds, put it live with the controls you choose, and then take what works across your client base.
The new Rewst platform is available today for new customers. If you're already a customer, Rewst Classic remains fully supported and under active development. We’re taking a phased approach to moving existing customers to the new platform to make the transition as efficient as possible. We’ll share more about migration options and timing as that work progresses.