Cy vs Scarlett.

Cy and Scarlett. are both ai agent apps tracked by AIDiveForge. Below is a side-by-side comparison of pricing, capabilities, platforms, and ownership — sourced from each tool's live website and verified before publishing.

Cy

Cy lives inside Slack and connects to your existing tool stack — CRM, inbox, LinkedIn, accounting software, ad accounts — executing multi-step jobs without a handoff back to you. The vendor demonstrates this with accounts receivable chasing, outbound sequence management, influencer pitching, and weekly reporting, all running on a schedule without a trigger from your team. Because there is no canvas to configure and no workflow builder to learn, setup is fast and the barrier to delegation is low. The ceiling appears when you need branching logic, conditional routing, or exceptions handled differently by account type — the page describes plain-English instructions, not configurable decision trees. Teams that need auditable step-by-step control over what Cy does when something goes wrong will find the abstraction uncomfortable.

Scarlett.

The agent runs 24/7 across messaging channels, autonomously completing multi-step tasks: a patient asks about availability, Scarlett checks the schedule, books the slot, and fires a reminder — no staff action required. For a single-doctor practice or a business with two to ten staff, that coverage is the core value proposition. The vendor states HIPAA alignment, which matters the moment you are handling patient data in a regulated environment. The scraped page is thin on integration specifics, so verifying EHR or PMS connector depth before committing is non-negotiable. Multi-location teams should validate whether workflow logic scales cleanly across sites or requires per-location configuration.

Attribute	Cy	Scarlett.
Pricing	Paid	Paid
Price	$20/mo	$97 USD / mo starting
Free trial	No	No
Open source	No	No
Has API	No	Yes
Self-hosted option	No	No
Platforms	Slack	Web, WhatsApp, Instagram, Facebook, SMS, Email, Voice
Pros	Executes multi-tool jobs end to end inside Slack without switching context, so your team is not the integration layer between CRM updates, email sends, and Notion logs. Scheduled always-on roles mean daily work like invoice chasing or outbound sequencing runs without a daily prompt, so recurring tasks do not slip when your team is heads-down on something else. Plain-English instructions replace workflow configuration, so there is no builder to learn and delegation does not require an ops specialist to set up. Connects to 1,000-plus integrations and syncs results back to the tools already in your stack, which means you are not maintaining a parallel system of record alongside Cy. Learns from each run and logs what worked, so repeated jobs compound rather than starting from scratch each cycle — the vendor's outbound example shows it updating a playbook automatically.	Autonomous booking and rescheduling across messaging channels, so appointment slots fill and shift without a staff member managing each exchange — missed calls stop becoming missed revenue. 24/7 availability for FAQ answering and clinical triage, which means a patient contacting the practice at 11 PM gets a response rather than an unanswered message that creates a no-show. Payment reminders sent with collection links as part of the same agent workflow, so billing follow-up does not require a separate tool or a staff member making manual calls. Vendor-stated HIPAA alignment, so the agent can handle patient conversation data in regulated health environments without the compliance re-architecture required by general-purpose chatbot platforms. Review requests triggered after visits as part of the automated flow, so reputation management happens consistently rather than depending on staff remembering to ask.
Cons	Plain-English instructions are the only control layer, so when a job hits an exception — a disputed invoice, a prospect who asked to be removed, an escalation that needs a different tone — there is no rule to write and no branch to configure. The task either runs incorrectly or Cy stops and waits. Teams with high exception rates will spend more time correcting outputs than they saved by delegating. There are no approval gates before Cy acts in live systems. If an outbound sequence goes to the wrong segment or an invoice is chased incorrectly, the action has already happened in HubSpot, Amplemarket, or your inbox before you see the thread summary. Teams that need to review before anything ships in a customer-facing context will need a different architecture — one that surfaces a draft and waits for sign-off. No self-hosted option exists, which is a hard stop for organizations under data residency requirements or in regulated industries where customer data cannot leave a specific environment. Teams in those categories move to a self-hostable alternative regardless of how well the workflow fits.	The vendor page does not describe EHR or practice management system connectors in detail — teams running on Epic, Athenahealth, or similar platforms cannot verify integration depth from public documentation, and a failed integration assumption at deployment means rebuilding the booking flow manually. No self-hosted option exists, which means patient conversation data routes through vendor infrastructure; for health systems with strict data residency requirements or security review processes that block SaaS-only vendors, this is a disqualifying constraint that sends teams toward self-hostable alternatives. The agent's autonomous loop works for linear tasks like booking and reminders, but multi-step conditional triage — where the next action depends on what the patient said two messages ago — is not documented as supported; teams needing that logic will add a separate automation layer and maintain two systems.

Bottom line

Only Scarlett. exposes a public API. Choose based on which difference matters most for your workflow.

Frequently asked questions

What is the difference between Cy and Scarlett.?

Cy is Paid, while Scarlett. is Paid. Compare pricing, free trial, API, platforms, and pros/cons in the table above on AIDiveForge.

Is Cy better than Scarlett.?

It depends on your workflow. Use the side-by-side attributes (pricing, open source, API, self-hosted, platforms) to decide. AIDiveForge does not rank a universal winner — we publish verified facts so you can choose.

Cy vs Scarlett.: which should I pick?

Pick Cy if its pricing model, openness, or platform fit matches your constraints; pick Scarlett. otherwise. Check free-trial availability on each listing if you want to test before committing.

Comparison data is sourced and verified by the AIDiveForge data pipeline. AIDiveForge is editorially independent.