Feature maturity
Forte uses three public maturity states. The state describes access and change expectations; it does not replace the Terms of Service, an order form, or an effective SLA.
| State | Access | Intended use | Change and support expectation |
|---|---|---|---|
| GA | Available to all accounts | Production workloads | Supported interface; material breaking changes require migration guidance |
| Open Beta | Available to all accounts | Evaluation and production use that can tolerate interface or limit changes | Supported, but behavior, limits, and pricing may change before GA |
| Closed Alpha | Enabled for a limited group | Workloads reviewed with Forte | Interface, limits, availability, and operations may change; no GA commitment unless agreed in writing |
Current feature matrix
| Surface | State | Notes |
|---|---|---|
| Services | GA | Containerized backend deployments, managed ingress, scaling, requests, and logs |
| Websites | GA | Static and server-rendered deployment with CDN delivery |
| Users | GA | Contact verification, sessions, passwords, Google sign-in, MFA, and administration |
| Payments | GA | One-time payments, saved methods, ACH, subscriptions, tax, and triggers |
| Actions | Open Beta | Recurring and one-time Service invocations with retries and history |
| Databases | Closed Alpha | PostgreSQL and MongoDB-compatible managed storage; tier capabilities differ |
| Content | Closed Alpha | Media processing, moderation, storage, and CDN delivery |
| Direct object storage | Closed Alpha | Interface is being validated with a limited group |
How to plan around maturity
For a Beta or Closed Alpha dependency, document fallback behavior, export needs, acceptable downtime, and the interface changes your team can absorb. Ask Support to confirm any contract, regional, retention, backup, or capacity requirement that is not stated in the relevant documentation.
Maturity changes are recorded in the changelog.