Asteris for WordPress — Roadmap

The roadmap is public on purpose. Items that are committed are marked committed. Items that are maybe are marked maybe. Items that have been deprioritised stay listed with a note so you don’t have to guess whether we forgot.

Founder customers have direct say on the v1.x roadmap. If you want to vote on what ships next, the Founder 500 launch is where that happens.


Shipped in v1.0

All 11 v1.0 modules are built and in pre-launch QA:

  1. Security + Login + 2FA
  2. SEO + AI Suite (flagship)
  3. Performance (post-research v2 spec)
  4. Forms
  5. SMTP + Email Logs
  6. Activity Log + Site Health (shared with Asteris for WooCommerce)
  7. Analytics + Pixels
  8. Image Optimisation
  9. Backups + Migration
  10. Code Snippets
  11. Accessibility scanner

See /modules for what each one ships.


Committed for v1.1 (post-launch, ordered by priority)


Under consideration (not committed)

Items here might ship in v1.x or might not. Founder votes break ties.


Deliberately out of scope

Things we’ve actively decided not to do (or not in v1.x):

See what Asteris doesn’t do for the full scope-limits page.


Cadence

We ship every Friday during launch. Even if a release is small, there’s a release. Updates land via the WordPress.org plugin updater (Free) and the plugin’s built-in updater (paid licences).

The changelog is the source of truth for what has shipped.


How to influence the roadmap

Every feature request gets a reply explaining which bucket it landed in: committed, under consideration, or out of scope (with a reason).


See also