Rewst review

Rewst is a managed automation platform for MSPs: a shared orchestration layer between service desk tools such as a PSA and endpoint tools such as an RMM. It connects the tools an MSP already uses and runs repeatable work across them, rather than replacing the PSA or RMM. The product also includes client-facing forms, apps, dashboards, and portals, with automation behind those interfaces.

Its Rewst Agent can answer questions across connected tools, perform one-off tasks, and help build workflows, forms, and apps. Teams can set permissions for publishing, track and version builds, and run work for a selected client tenant. The vendor says credentials stay scoped to that tenant and activity is logged, including who approved a run. That makes Rewst an operational control plane for work that crosses tools and clients. It is not presented as a library, CLI, or self-hosted server; the product is described as a platform accessed from one login.

The vendor homepage describes connecting tools across an MSP stack, including Microsoft, Google Workspace, PSA, RMM, and documentation platforms. It does not name a specific API protocol, SDK, programming language, or CLI. Treat Rewst as a workflow-building integration platform, not a documented developer library: confirm supported connectors, API access, webhooks, authentication methods, and SDK availability in the vendor's technical docs before planning an integration.

There are signs of more technical integration paths, but they come from users rather than the homepage. A Reddit commenter says they used Claude through MCP with Rewst; another says the platform can use a Swagger file or API documentation to build an integration. These reports are useful leads, not a substitute for vendor documentation or a support commitment. Ask whether your required tools have maintained connectors, how custom integrations are versioned, and whether workflow definitions can be reviewed or managed outside the platform. The vendor says builds remain visible and editable.

Rewst lists a custom Platform plan priced per client per month, with no published starting price. The plan includes unlimited users, unlimited automations, 30-day execution history, and an AI allowance equal to 5% of the monthly invoice. There is no free plan, and trial availability is not published. The pricing details are marked low confidence, so confirm the current quote and terms with Rewst before budgeting.

The plan is priced around the client book rather than a stated per-seat or per-execution rate. The published details do not give a usage rate for runs, request limits, or overage prices, so ask how the quote changes as you add client organizations and what happens when AI usage exceeds its allowance. Rewst says customers can bring their own AI provider key; that usage is billed directly by the provider with no Rewst markup. Annual billing terms are not published. Budget for implementation and ongoing workflow maintenance as well as the subscription, since Reddit users report that building out the platform can take substantial staff time.

Rewst is presented as a vendor-managed platform, not as software to install on your own servers. The vendor does not publish an open-source license or a self-hosting option, so treat source availability and deployment outside Rewst as unconfirmed. The vendor also does not publish a data-export or workflow-export path on its homepage; ask how to retrieve execution history, credentials metadata, workflow definitions, forms, and client data before signing.

The product's tenant model and integrations may tie workflows to Rewst's platform and connector behavior. That does not make migration impossible, but it means an exit plan matters: identify which builds can be exported, what needs rewriting, and how credentials are rotated if you move. Reddit users describe both migrating onto Rewst and moving away from it, but those posts do not establish a standard migration process.

The vendor describes tenant-scoped credentials, activity logs, and permissions for approving and publishing automations. Those controls are relevant to MSPs running jobs across customer environments, but they are not a complete security or compliance assessment. Before putting production workflows on the platform, confirm the available audit-log retention, role controls, incident process, data residency, compliance reports, backup behavior, and recovery options. The plan lists 30-day execution history; ask whether longer retention is available and what it costs.

There is no published request or execution limit in the plan details, so check how concurrency, timeouts, retries, and rate limits work for your connected services. Reddit reports are mixed: one thread alleges slowness and outages over several months, while other commenters praise the newer platform and report building automations faster. These are user accounts, not an uptime record. Ask for current status history and contractual service levels, and test failure handling with the tools and tenant volumes your MSP depends on.