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

Good to know

• Stored-card charging needs developer work for real gateways. Card payments and renewals work out of the box on the simulated gateway. Charging a saved card for a renewal on Stripe, Razorpay and PayPal is not finished: those chargers are guarded stubs that refuse to run until a developer completes them. Plan this work before you take live renewals.
• Arabic is partial. Only the home page, the navigation and the account overview are translated and mirrored. The rest of the site and the admin panel are English.
• No mobile apps. Subscribers use the responsive web account.
• Rare concurrency edge cases remain. Billing, cancellations and refunds lock rows in one fixed order, and nine race checks on MySQL pass, including Pay now against Cancel. A few unusual paths are known and listed in the documentation: cancelling between a renewal invoice being created and charged does not void that open invoice; a coupon's remaining boxes are not restored when a renewal invoice is voided; two refunds issued at the same instant can both try to refund the same card part; and the capacity forecast can under-count a subscriber who skipped an earlier edition and has no next edition.
• Live gateways, email and SMS were not tested with real accounts. Run your own sandbox payments before taking real ones.
• Databases: MySQL 8 and SQLite were tested for seeding and the checks; MariaDB and PostgreSQL were not.
• Name: Lidwick is a working name checked by a web search only, not a trademark clearance. Check it before you launch under it.
• No hosted demo. The brand, people, products and addresses in the screenshots are fictional.