Skip to main content
UpdateFix
v1.0.2

Week in review

This week we focused on launch polish — pricing clarity, infrastructure reliability, API accuracy, and security hardening.

Updates

  • **PRO plan pricing updated to 59/monthThePROplanisnow59/month** — The PRO plan is now 59/month (previously 29).BUSINESSremainsat29). BUSINESS remains at 99/month. If you are on an existing PRO subscription, your current rate is honoured. View plans
  • AI features infrastructure updated — The AI assistant suite (lease analyser, maintenance classifier, rent recommender, communication drafter, and more) is powered by our AI provider. This update improves response speed and reliability. AI features are available as a private beta and may not be accessible to all hosted users. Learn more
  • Accurate rate limit responses — API rate limit responses (HTTP 429) now return a structured body with error, message, and retryAfter fields, along with an X-RateLimit-Reset header. If you are building against the API, you can now reliably parse rate limit responses and implement proper backoff. Learn more
  • Honest marketing copy — The landing page has been updated to remove claims about features that are not yet available, including a 14-day free trial, churn alerts, and QuickBooks sync. A beta status banner and a product roadmap section have been added so you know exactly what is live today and what is coming next.
  • Working contact form — The contact page now has a fully functional form. You can reach us directly from the site without needing to send a separate email.

Bug fixes

  • Fixed an issue where sign-in could hang indefinitely if the rate limiter was temporarily unreachable. Authentication now falls back gracefully with a three-second timeout, so you can always log in.
  • Fixed a cross-site scripting vulnerability on the pricing page where HTML content was rendered unsafely. The page now uses safe text rendering throughout.
  • Fixed rate limit documentation that previously showed an incorrect response schema. All 429 responses across the API spec now match the actual response format.
Last modified on June 21, 2026