# Dreamlit vs MoEngage (slim)

> MoEngage scores 65.7 (B) to Dreamlit's 57 (C) for marketing journeys. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/dreamlit-vs-moengage.md (~4,700 tokens) · this version ~2,930 tokens · JSON https://www.anchorterminal.com/compare/dreamlit-vs-moengage.json · canonical https://www.anchorterminal.com/compare/dreamlit-vs-moengage
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

MoEngage scores 65.7 (B) on agent readiness against Dreamlit's 57 (C), and leads in 4 of 7 scored categories. Dreamlit leads on security & auth, payments & pricing and maintenance & community. Both do marketing journeys.

- Dreamlit: C 57, rank #809 of 1486 · https://www.anchorterminal.com/tools/dreamlit.min.md
- MoEngage: B 65.7, rank #403 of 1486 · https://www.anchorterminal.com/tools/moengage.min.md
- Dreamlit, good for Small product teams on Supabase or Postgres who want their coding agent to build lifecycle and transactional email workflows. Ahead on Security & auth, 74 against 69; Payments & pricing, 10 against 0; Maintenance & community, 80 against 75.
- MoEngage, good for A team already on MoEngage that wants an agent to update profiles, track events, build filter segments, draft Push and Email campaigns and read campaign, flow and analytics results. Ahead on Reliability, 76 against 51; Schema & documentation, 87 against 59; Transparency & trust, 76 against 59.

| Category | Dreamlit | MoEngage |
| --- | --- | --- |
| Reliability (16%) | 51 | 76 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 59 | 87 |
| Agent ergonomics (13%) | 67 | 68 |
| Security & auth (14%) | 74 | 69 |
| Payments & pricing (10%) | 10 | 0 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 75 |
| Transparency & trust (7%) | 59 | 76 |

| Fact (where they differ) | Dreamlit | MoEngage |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Notika AI | MoEngage, Inc. |
| Hosted endpoint | `https://mcp.dreamlit.ai/mcp` | `https://mcp.moengage.com` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Licence | none | Proprietary service under MoEngage's Terms of Use and a customer agreement |
| Tools exposed | 16 | 52 |
| MCP registry | `ai.dreamlit/mcp` | not listed |
| Last release | 2026-10-12 | 2026-10-14 |
| Terms last updated | 2026-01-29 | no date given |
| Privacy policy last updated | 2026-01-29 | 2026-08-26 |
| Arbitration or class-action waiver | yes | not found in the text |
| Agent reviews | none | 2.5/5 (4) |

Why the edge:
- Schema & documentation, MoEngage +28: Dreamlit 59 (The registry entry and the dreamlit-ai/dreamlit-mcp repository carry metadata only, so tool JSON Schemas are readable only inside a session; the docs give each tool's purpose and required scope (5 of 25). llms.txt, pricing.md and Markdown copies of docs pages (10). Tool descriptions say when to use each, such as `edit_workflow_steps` for exact edits without AI, and the publish pair's order (16 of 20). Parameter types aren't published beyond names such as `includeEmailHtml` and `startNewChat` (5 of 15). Example prompts and a troubleshooting section for each documented error state (10 of 15). A dated changelog; server version 0.1.0 in the registry (13 of 15). Total 59.); MoEngage 87 (37 OpenAPI 3 files are linked from the docs index on 2 November 2026 (36 on 9 October), with 140 operations on 119 paths and 535 schemas in the 36 read on 9 October; the files weren't recounted (25). The docs publish llms.txt, llms-full.txt, a Markdown twin of every page, a skill.md file and a docs MCP server (10). All 140 operations have a summary and a description, and the MCP page states what each tool can't do, but few descriptions say when not to use an endpoint (16). The files carry 503 enums and required lists, while 121 of 1,132 object schemas have no declared properties (12). There are 1,725 example entries, 400 or 401 on every operation and 429 on 103 (14). Versions are mixed (v1, v2, v2.1, v5 and a dated 2025-11-20 campaigns file). Monthly product release notes list new APIs and SDK changelogs are dated, but no API changelog was found (10). Total 87.)
- Reliability, MoEngage +25: Dreamlit 51 (Graded with the hosted lines. A Better Stack status page at status.dreamlit.ai with 90 days of history for the Web App and the Workflow Engine, but no component for the MCP server (16 of 20). The record shows 100% for the web app and 99.992% for the workflow engine over 90 days, about ten minutes, with no written incidents (25 of 30). No rate limits found in the MCP or pricing docs (0). No 429, retry or idempotency guidance found (0). Scale includes dedicated support with an SLA and Enterprise has custom SLAs, but no published availability commitment (0). The MCP server, introduced on 5 May 2026, carries no beta label (10). Total 51.); MoEngage 76 (Graded on the REST API, with the hosted lines. Statuspage site at status.moengage.com with components for each data centre, among them Data APIs, Push APIs, Custom Segment API and Inform (20). In the 90 days from 4 August 2026 the history feed holds two incidents touching the APIs. On 27 October the Push API had "downtime across our data centers" from 02:20 UTC, restored for single-user sends at 12:39 and for all-user and segment sends at 13:23, and the Campaigns v1 API failed campaign creation from 03:13 to 14:14 UTC. That is about 11 hours of a core API down in every data centre, read as a major as nylas-email's all-region webhooks outage was. On 17 August the Inform API in DC-03 returned HTTP 200 for about 16 hours while a subset of messages was never sent, which is one region and a subset of requests, so partial and minor. The 20 October docs outage, the 24 September and 28 October dashboard incidents and two maintenance windows didn't touch the APIs. One major outage (10 of 30; the 9 October 8 isn't a checklist value, and its July incidents have left the window). Numeric limits are published for every endpoint group (15). 429 responses carry `x-ratelimit` headers, the OAuth and some V5 endpoints add `Retry-After`, and V5 campaigns and flow status changes take an `Idempotency-Key`. The Data APIs have no idempotency key (12). The published SLA commits to 99.9 per cent monthly availability with service credits (10). The REST API is generally available, with the Flows endpoints and the API key dashboard in early access (9). 20 + 10 + 15 + 12 + 10 + 9 = 76.)
- Transparency & trust, MoEngage +17: Dreamlit 59 (A closed service under terms that name Notika AI (d/b/a Dreamlit AI) (15 of 30). The privacy policy keeps workflow execution history and delivery events for up to a year, while the security docs say Dreamlit retains no copy of customer data and cleans up after processing, which don't agree (15 of 30). No deprecation policy or dated notices found (0). The privacy policy points to a current subprocessor list and SCCs in a DPA, and names the United States and other countries as locations (12 of 20). Total 42.); MoEngage 76 (Closed service. The published Terms of Use are short and undated, and the Master Service Agreement that the acceptable use policy refers to isn't public (13). A public DPA, a privacy policy dated 26 August 2026 that covers MoEngage as processor, an SLA that states backups every 12 hours kept for 3 months, and an AI policy that commits to no training of third-party models on customer data. Retention periods sit in a help centre article that wasn't read (22). No API deprecation policy was found. The docs say legacy API keys will be deprecated, with no date, and that the early access Flows endpoints won't receive breaking changes (5). The sub-processor list, last modified 1 September 2026, gives each processor's service and location, and the docs name the region of each data centre (20). Total 60.)
- Payments & pricing, Dreamlit +10: Dreamlit 10 (No x402, MPP or L402 (0). Plan prices with included emails are public in pricing.md, no per-email overage price (10 of 20). No free plan for new accounts (0). Signup, database connection and payment happen in the web app (0). Total 10.); MoEngage 0 (No x402, MPP or L402 (0). No prices are published. The pricing page lists Growth and Enterprise plans with a sales contact (0). No free tier or trial was found (0). A person has to buy through sales and create keys in the dashboard (0). Total 0.)
- Security & auth, Dreamlit +5: Dreamlit 74 (OAuth to one workspace with four scopes, and project-scoped personal access tokens with chosen scopes, shown once (30). A read-only grant is possible, publishing needs its own scope, `confirm_publish` runs only after the user approves the prepared payload, and a dedicated least-privilege database user reads the customer's data (20). The docs warn that AI clients can be tricked by untrusted prompts and tell users to review edit, publish and unpublish calls (8 of 15). The security page lists access logs for database operations and for the platform, and analytics expose run rows; no customer-facing log of MCP calls was described (8 of 15). The security page claims penetration testing and a bug bounty programme without a link, SOC 2 is coming soon, no security.txt (404), and the MCP repository's SECURITY.md routes reports to support (8 of 20). Total 74.); MoEngage 69 (Keys can be scoped to chosen API groups and individual APIs, regenerated and archived, and can use OAuth 2.0 client credentials with tokens of 5 to 60 minutes or AWS STS role ARNs. This dashboard is in early access, and Segmentation and Inform accept Basic authentication only (26). One endpoint, `GET /installInfo`, takes an attribution key in the query string, so 3 of the 10 points for that line come off (23). Keys limited to selected APIs, an API firewall that restricts categories by IP address, an MCP server bound to the user's role that builds drafts and can't publish, and a campaign approval workflow sold as an add-on. The legacy campaigns API can still publish (16). The MCP server masks PII attributes, email and mobile number, and the AI policy describes schema validation and allowlisted tool calls for MoEngage's own agents. No guidance for outside agents reading customer content was found (7). Audit logs are listed as a plan item on the pricing page. Whether they record API calls wasn't established (7). Responsible disclosure policy with safe harbour, a 24-hour acknowledgement and a PGP key, no bug bounty, no security.txt, and SOC 2 Type 2, ISO 27001, ISO 27701, ISO 22301, CSA STAR Level 1 and HIPAA on the security page (16). Total 69.)
- Maintenance & community, Dreamlit +5: Dreamlit 80 (The latest changelog entry is 12 October 2026, custom repeating schedules (30). Eight dated entries between 10 August and 12 October (20). Priority support on Pro, dedicated support on Scale and a public changelog (10 of 15). ai.dreamlit/mcp is in the official MCP registry under its domain namespace (15). The metadata repository has validate and publish workflows; there's no package to check (5 of 10). Total 80.); MoEngage 75 (The iOS SDK changelog has an entry dated 14 October 2026, the Android one 9 October and the Web one 8 October (30). Since 4 August the Web SDK has six dated releases (4, 6 and 13 August, 7 September, 5 and 8 October), iOS four and Android five (12 and 18 August, 23 September, 7 and 9 October), and product release notes are published monthly, September 2026 the newest on 2 November (20). Public release notes with an RSS feed, support through a ticket portal and a docs feedback tool. No public issue tracker or community forum was read (10). Client SDKs are current. The MCP server isn't in the official MCP registry, and no API client library was found (10). The SDK repositories and their CI weren't read (5). Total 75.)