Skip to content

SaaSOS Runtime Roadmap

A starter kit that gets easier to trust with every release.

We are building SaaSOS around one practical outcome: helping small teams move from purchased source code to a product they can confidently own, extend, deploy, and maintain. This is our current direction, not a promise of fixed dates.

Actively maintained

Current focus: setup confidence and product hardening.

Updated July 2026

Direction changes when customer evidence changes.

No invented deadlines

Work is called shipped only when a verified release is available.

✓

Shipped foundation

Available now

Available in the commercial Runtime today and maintained through versioned releases.

  • Source-owned React and Laravel Runtime with multi-tenancy, authentication, permissions, billing foundations, and audit trails
  • Commercial license, customer portal, documented setup path, and support boundary
  • Reusable listing, form, dialog, reporting, settings, and platform patterns for buyer-built modules
  • Verified release artifacts tied to recorded versions, release notes, and customer download access
2

Now: make the first week effortless

Active focus

Our active focus is reducing uncertainty between download and a clean, understood local Runtime.

  • Tighter setup diagnostics and clearer supported-environment guidance
  • More reliable stock-Runtime checks across frontend, backend, permissions, and tenant boundaries
  • Sharper deployment, security, accessibility, and troubleshooting documentation
  • Release notes that explain customer impact, upgrade considerations, and verification steps
3

Next: upgrade with confidence

Up next

Once the first-run path is consistently strong, the focus moves to making long-lived customer projects safer to update.

  • Practical upgrade notes for migrations, configuration changes, and compatibility risks
  • A clearer compatibility matrix for supported PHP, Node.js, database, and hosting combinations
  • More stable extension contracts and examples for payments, mail, storage, authentication, and webhooks
  • Regression coverage around permissions, operational workflows, and reusable platform components
4

Then: operate with confidence

Later

Production guidance will grow where it can remove repeatable operational mistakes without pretending to run customer infrastructure.

  • Deeper recipes for queues, scheduled jobs, backups, restoration checks, storage, and secret rotation
  • Observability and incident-response guidance that remains provider-neutral
  • More complete examples for secure file handling, payment reconciliation, and audit review
  • Deployment recipes chosen from real buyer environments and recurring support questions
5

Exploring with customers

Exploring

These ideas are not committed. They move forward only when buyer demand, maintenance cost, and product fit support them.

  • Additional reusable import, reporting, and operational patterns
  • Focused product examples that demonstrate composition without becoming vertical ERP bundles
  • Broader automated compatibility checks where they produce reliable signal
  • Customer-approved implementation stories with honest scope, tradeoffs, and outcomes
6

How priorities are chosen

Decision rule

The sequence can change as evidence changes. We prioritize work that improves the product customers already own before adding a wider surface area.

  • Security, tenant isolation, and data integrity
  • Setup success and time to first useful customization
  • Upgrade safety and backward compatibility
  • Recurring support patterns reported by real buyers
  • Long-term maintenance cost for customers and the Runtime

Help shape what comes next

What is slowing down your launch?

Tell us the setup, upgrade, deployment, or platform problem that costs you the most time. Repeated customer problems carry more weight than feature-list pressure.

Share roadmap feedback
See what has shipped