What are the limitations of DEV3 Mailtide I should know before buying?

What you should know before buying

• The demo and tests use a simulated sending server: nothing is delivered. Add your own SMTP, Amazon SES (via SMTP), Mailgun or Postmark credentials to send for real. The SES, Mailgun and Postmark drivers were written to the providers' public documentation and have not been run against live accounts.
• It does not test inbox placement or spam scores: the linter is only a lint.
• SMTP cannot be made idempotent, so a crash after the relay accepted a message can send that message twice on retry.
• Bounce and complaint mail (DSN and ARF) is parsed from .eml files with a command; fetching it from a mailbox is up to you.
• Plans are billed by the operator through the platform gateway (simulated by default; Stripe, Razorpay and PayPal drivers are present). Workspaces cannot connect their own payment account.
• The editor is best on desktop. DNS checks use your server's resolver (the demo simulates them). Open and click geography is not collected.
• The demo seed shows about 85,000 contacts, 1,000 campaigns and 1.6 million recipient rows and takes a minute or two on MySQL.
• Web only: there are no mobile apps. Node.js is not needed (assets are prebuilt).