By David,
Two launches landed in the same week of October 2026, and both of them will come up in your next vendor conversation.
On October 13, Rewst made its new, AI-native automation platform available in every market. Its headline is the Rewst Agent: describe a process in plain English and it builds the workflow, form, dashboard or client app for you. Two days later, on October 15, Neo Agent arrived on the Pax8 Marketplace. Neo is an AI service desk agent: it picks up tickets in your PSA, works out what each one needs, does the work and closes it.
We get asked how Atlas AVD compares to both. The honest answer is that these are three different jobs. Neo is a technician. Rewst is a builder. Atlas AVD is the platform that runs your customers' Azure Virtual Desktop estates. This post explains what each one does, what it costs, how much each lets AI do on its own, and how the three fit together in one MSP stack.
The short version: Neo Agent is an AI first-line technician that works tickets inside ConnectWise, Autotask, HaloPSA, Syncro or ServiceNow. The new Rewst is an automation platform whose agent drafts workflows, forms and client portals that a person approves before they go live. Atlas AVD deploys, scales, images, monitors and cuts the cost of Azure Virtual Desktop, from inside your own Azure tenant, and includes ticketing, endpoint management, documentation and a read-only assistant. If AVD is part of your service, you need a platform that runs it. Neo and Rewst can sit on top.
Neo Agent and Rewst details below come from each vendor's public website and announcements as of October 2026, linked in the Sources section. Vendors change products and pricing, so confirm current details directly.
What each one is for
| Neo Agent | The new Rewst | Atlas AVD | |
|---|---|---|---|
| The job | Work tickets end to end, like a first-line technician | Build and run automations, forms, dashboards and client apps across your tools | Deploy, run, automate and cost-optimize Azure Virtual Desktop |
| What you give it | A plain-English brief, your playbooks and your documentation | A plain-English description of the outcome you want | Your customers' Azure tenants |
| Where it acts | Your PSA, RMM, documentation and identity tools | Any of its connected integrations | Host pools, session hosts, images, scaling and the endpoints around them |
| Where it runs | Neo's hosted service, with a choice of data region | Rewst's hosted platform | Your own Azure tenant |
| Priced by | Monthly plans sized in credits | Per client organization, in bands | Per tenant you manage |
The useful way to read that table is top to bottom, not left to right. A ticket that says "the accounting team can't get onto their desktops" needs someone to work the ticket, it may need an automation that runs every time it happens, and it definitely needs a platform that can see the host pool, the image and the FSLogix storage behind those desktops.
Neo Agent: an AI technician for your service desk
Neo describes itself as an AI workforce for MSP service desks. You brief it in plain English rather than building rules, and it handles repetitive tickets from start to finish: triage and dispatch, first-line fixes, user onboarding, security alert response and RMM remediation, escalating to a person when a ticket needs one. It also runs scheduled work, such as Microsoft 365 compliance checks, QBR reports and sweeps for stale tickets and SLA risk.
Where it connects. Neo lists native PSA support for ConnectWise PSA, Autotask, HaloPSA, Syncro and ServiceNow, RMM and remote access tools including NinjaOne, Datto RMM, N-able, ConnectWise Automate, Kaseya VSA X and ScreenConnect, documentation in IT Glue, Hudu, SharePoint, Confluence and Notion, and identity through Microsoft Entra ID, Active Directory, CIPP and Okta.
How much it does on its own. You choose, per tool, whether Neo has no access, read access or write access. Test mode runs its actions as notes first, so you can watch it work your real tickets before it changes anything. Sensitive actions wait for a technician's approval, and low-risk work can run without one once you allow it. Every step is written to an audit log.
What it costs. Neo lists six monthly plans sized from 2,500 to 100,000 credits, starting at $1,300 a month for its Starter plan, month to month, with no setup fee. Through Pax8 it bills on your existing Pax8 invoice, and you can trial it for 14 days against your own tickets. An AI phone agent and a branded end-user chat bot for Microsoft Teams are add-ons.
What it isn't. Neo works tickets in the tools you already have. It doesn't deploy host pools, build images or scale session hosts, so for AVD it is only as good as the platform it can read and act through.
The new Rewst: an AI that builds your automations
Rewst has been the MSP automation platform of choice for a while, and the new version keeps that job but changes who can do it. Instead of an automation engineer wiring every step by hand, you describe the outcome and the Rewst Agent builds it: the workflow, including its code, data transformations and conditions, plus any form, dashboard or client-facing app around it. Everything it builds lands on the same visual canvas engineers already use, where you can inspect each step and take over.
How much it does on its own. Rewst is explicit that the Agent can't create, update or publish a workflow or form without approval, and it must ask again before publishing. Publishing is a separate permission you give to specific people. Credentials stay scoped to the client they belong to, AI access is granted separately from the integration itself, so you can revoke it without breaking production automations, and Rewst keeps a per-client record of what ran.
What it reaches. In its 30-day Early Access, Rewst says more than 110 MSPs used 340 distinct integrations and ran over 1.25 million workflows. A Rewst MCP server lets your team use the Agent from an AI assistant they already use.
What it costs. Rewst prices per client organization, with lower per-client rates as you grow, and includes every feature, unlimited users and unlimited automations at every size. Every account gets an AI allowance worth 5% of its monthly invoice, or you can bring your own AI key and pay your provider directly. Rewst doesn't publish its per-client rates, so you'll need a quote.
What it isn't. Rewst is an orchestration layer. It can reach Microsoft environments through its integrations, so an engineer could build AVD workflows with it, but you would be designing, testing and maintaining that logic yourself, for every customer. Existing customers also stay on Rewst Classic for now while Rewst phases in migration.
Atlas AVD: the platform that runs the desktops
Atlas AVD is not an AI agent that sits on top of other tools. It's the platform that does the AVD work itself, and it runs as an app in your own Azure tenant, so your customers' data stays there.
- Deploy and run AVD: host pools, session hosts, application groups and workspaces across every customer tenant from one console, with cross-tenant dashboards for capacity, cost and health.
- Automation built for AVD: autoscale schedules, DrainGuard to clear out idle VMs, Adaptive Density to tune session limits and Adaptive Quota to request Azure capacity, each with previews, confirmations and kill switches. The automation best practices guide covers those guardrails.
- Safe image updates: staged rollout rings that bake, check a health score, and roll back to the previous image on their own if a ring regresses. The rollout deep dive walks through it.
- The work around the desktops: Atlas Flow ticketing, time and billing (in preview), Atlas Reach endpoint management and remote support, and Atlas Vault for client credentials and documentation, under one sign-in and one audit trail.
- An assistant that answers, not acts: Atlas Advisor answers questions about your environment in plain language and surfaces savings and risks. It runs on your own AI provider key (OpenAI, Anthropic, xAI or Azure OpenAI), works without one through a built-in engine, and is read-only: it doesn't make changes to your environment.
What it costs. Atlas AVD is $199 per tenant a month, with every AVD feature, unlimited AVD users and unlimited technicians. The optional MSP Capabilities upgrade adds Atlas Command and white-label branding for +$50 per tenant a month. A customer who grows from 80 to 400 users doesn't change your bill.
Who lets AI act on its own?
This is the question your security-minded customers will ask, so it's worth putting the three side by side.
| Neo Agent | The new Rewst | Atlas AVD | |
|---|---|---|---|
| AI writes to your systems | Yes, within the access you grant each tool | Only through workflows a person has approved and published | No. Atlas Advisor is read-only |
| Human approval | Technician-in-the-Loop for the actions you choose | Required to create, update and publish | Not needed for Advisor; Atlas automation asks for confirmation on destructive changes |
| Dry run | Test mode writes notes instead of changes | Inspect and test on the canvas before publishing | Monitoring-only mode and "If DrainGuard ran right now" previews |
| Record of what happened | Audit log of every step | Per-client log of what ran | Full audit trail and change history per tenant |
| AI model | Neo's | Rewst's allowance, or your own key | Your own provider key, or none |
None of these is wrong. They reflect three different jobs. A technician has to change things to close a ticket. A builder produces automations that run without it. The platform that owns your customers' desktops keeps AI to answering questions and leaves the changes to automation you configured and people you trust.
How the three fit together
Here is a Monday morning with all three in place:
- Atlas AVD notices first. A host pool's session hosts report unhealthy. Atlas alerting fires to SMS, Teams, Slack or a webhook, and an Atlas Flow automation rule can open a ticket for it, add to that ticket while the problem lasts and resolve it when the problem clears.
- The ticket reaches your PSA. If you run ConnectWise Manage, Atlas syncs tickets with it in both directions. Otherwise, the alert webhook can post to whatever opens tickets for you.
- Neo Agent works the ticket. It reads the ticket, checks your playbook and documentation, and decides whether this is something it can handle or one to escalate to your on-call engineer.
- Rewst runs the repeatable part. If the same fix happens every week, a Rewst workflow can do it. Atlas API keys let a tool you trust call a defined set of Atlas endpoints, such as listing Atlas Reach devices or running an approved script from your library. A key can never upload new script content.
- Atlas AVD fixes the root cause. The image that broke the hosts gets rolled back by its rollout ring, DrainGuard clears the idle VMs, and the audit trail records all of it for the customer's next review.
To be clear about what exists today: Atlas has no native Neo Agent or Rewst connector. The joins are your PSA, alert webhooks and the Atlas API.
Which do you need?
- Your service desk is drowning in repetitive tickets and you want an extra pair of hands, not another tool to build in: look at Neo Agent.
- You have dozens of processes that should run the same way every time and want someone who understands the problem, not only your automation engineer, to build them: look at the new Rewst.
- You run Azure Virtual Desktop for your customers, or want to: you need a platform that deploys, scales, patches and reports on it. That's Atlas AVD, and it makes the first two more useful, because every ticket they touch has real data and a real fix behind it.
If you already run Neo or Rewst, nothing about Atlas AVD asks you to stop. See MSP pricing, read how Atlas compares with other AVD platforms on Atlas AVD vs Hydra, or start a 30-day trial and stand up your first customer tenant this week.
Sources
- Rewst: Rewst launches new automation platform globally (October 13, 2026)
- Rewst: Welcome to the new Rewst
- Rewst: Pricing
- Neo Agent: Neo Agent brings its AI service desk workforce to the Pax8 Marketplace (October 15, 2026)
- Neo Agent: neoagent.io