From a plain-English request, Rewst can answer questions across connected tools; build workflows, forms, dashboards and client portals; and keep work governed at the client level.
Tampa, FL (October 13, 2026) — Rewst today announced that its new automation platform is now available in all markets. Anyone who understands the work can describe the outcome they need in plain English, and the Rewst Agent can build it, from workflows and forms to dashboards and client-facing apps. Everything the Agent makes is visible and editable on a visual canvas, while a person remains in control of what goes live. Credentials and access stay scoped to the client they belong to.
The platform opened to Early Access in late June, following its preview at the company’s annual FLOW conference. Since then, more than 110 MSPs have used it. In a 30-day period, they ran more than 1.25 million workflows and 58 million tasks across 340 distinct integrations, building an average of more than 150 new workflows a day. Top use cases include turning security alarms into PSA tickets, keeping device inventory consistent across tools, and syncing accounts, roles, and licenses on a schedule.
General-purpose AI tools have made it easier to generate an individual automation. But running a growing portfolio of automations reliably and securely across an MSP’s client base and tech stack presents a different set of challenges.
Scripts and automations can end up scattered across individual machines and tools. Credentials may be embedded in scripts or reused across environments. Actions can cross multiple systems while the record of what happened remains siloed in vendor consoles. And someone still has to maintain the integrations, manage failures, and understand how everything fits together.
Rewst combines plain-English automation building with controls designed for the multi-client environment MSPs operate. Credentials stay scoped to the client they belong to, while role- and resource-based access lets the MSP determine who can work with each client and connected system.
The Rewst Agent can’t create, update, or publish a workflow or form without explicit approval, and it must ask again before publishing.
“With the new Rewst platform, people across our company will be able to use the Rewst Agent to draft a workflow and hand it to our integration engineers for refinement,” said John Snyder, CEO of Net Friends. “And yet we still have control. It doesn't feel like we've just opened things up and it's going to get wild and crazy.”
Rewst keeps a record of what ran in one place for each client, so teams can trace work routed through Rewst without piecing it together across individual scripts and vendor consoles.
“We didn’t want to bolt AI onto Rewst. We wanted to rethink the platform around what becomes possible when AI can securely understand and use the tools, workflows, and integrations our customers already rely on. The MCP layer is what makes that possible. It gives AI access to do what it needs to do without giving it uncontrolled access to the underlying systems, and it lets customers build on the automation investments they’ve already made. This is a much bigger foundation for where Rewst goes next.”
— Aharon Chernin, Founder & CEO, Rewst
Once an MSP connects its tools, Rewst becomes the secure orchestration layer across them. Whether the request comes through the Rewst Agent or a supported AI connection, the integrations, automation, credentials, permissions, and execution remain managed in Rewst. The same foundation can power a question asked across the stack, a one-off action, repeatable automation, or an experience delivered through a form, dashboard, or client-facing app.
A workflow can make a technician faster. A form can let someone without technical expertise initiate an automation. A dashboard can bring the right information together. And a client portal can let the client get something done without opening a ticket. Because all run on the same orchestration layer, MSPs can reduce tool sprawl, replacing point products while maintaining fewer integrations and permission models.
For MSPs, that means more than reducing manual work. The team they already have can support more clients and seats, senior builders can review and refine work instead of starting everything themselves, and the dashboards, reports, and portals clients see can become services the MSP packages and sells.
Not every task needs a workflow. Some work starts as a single question or action, and it can begin as soon as an MSP’s tools are connected. An MSP might ask whether this month's distributor invoice lines up with the contracts in its PSA, which clients are missing patches, or how many seats a client has added since its last renewal. Rewst can reach across connected systems and return one answer even when the data lives in several tools.
Rewst gives AI tools the team already uses controlled access to connected systems without requiring each technician to build and maintain their own integrations. AI access is granted separately from the underlying integration, so an MSP can change or revoke that access without disrupting production automations that depend on the same connection.
Where a single ask handles something once, automation handles the work that repeats: a user onboarding process that runs fifty times a month, multiple license reconciliations every billing cycle, or routine service requests like password resets.
An MSP describes the outcome it needs, and the Rewst Agent builds the workflow. A person can review, test, and refine the result before approving it, or open the visual canvas to inspect and edit individual steps when more control is needed.
Once published, the workflow runs on Rewst’s orchestration layer with the integrations, credentials, permissions, and client context it needs. The MSP owns the logic. Rewst runs the rails underneath.
The same automations and connected data can power forms, dashboards, reports, and client-facing apps, giving MSPs the option to replace standalone tools they would otherwise have to buy, integrate, and maintain separately.
A form makes sure an automation starts with the information it needs. The Agent can build the form, the workflow behind it, or both. Fields can appear or change based on earlier answers, while choices can populate dynamically from connected tools, such as showing only the group memberships available to a specific user. Forms can be built once and reused across clients, with branding, fields, and access adjusted where needed.
Apps can bring data and automation together in internal tools, dashboards, and client-facing services built around a specific job. An MSP might build a client onboarding wizard that coordinates dozens of steps across its PSA, Microsoft environment, and documentation tools, or a QBR scorecard that brings ticket trends, SLA performance, asset data, and security information into one client-ready view.
A client self-service portal can give clients a branded experience built around exactly what the MSP wants them to see and do. Clients can view dashboards, request services, check status, and trigger approved workflows such as password resets, access requests, and user onboarding or offboarding, all under the permissions the MSP sets.
An MSP describes the experience it needs, and the Agent builds the pages, actions, and automations behind it. One app can serve the entire client base, adapting branding, access, data, and available workflows according to who is viewing it. The result is a client-facing service connected to the same platform that runs and governs the underlying work.
The new Rewst platform is available worldwide today for new customers, with access expanding to existing customers over time. Until then, existing customers can continue building and running automations on Rewst Classic, which remains fully supported and under active development.
To learn more, visit https://rewst.io/platform
Rewst is the secure, multi-tenant automation platform built for managed service providers (MSPs) to orchestrate work across their tech stack and client base. Anyone on the team can ask the Rewst Agent questions that pull from connected tools, or describe what they need and have it create workflows, forms, dashboards, and apps. Rewst keeps each client separate and lets MSPs decide who can put work live. With an active automation Community, Rewst helps more than 1,500 MSPs scale their businesses and turn automation into services they can sell.
Want to figure out what we learned from early access and see live demos? Save your seat for our upcoming webinar on November 3rd.