Priced around applications
Review proposed FlowState Marsward plans for founders, studios and teams. Pricing is provisional; paid plans are not available yet.
One application. Its whole operational picture.
The proposed pricing unit is an actively monitored application, rather than a seat or an individual provider brand. The proposed monthly USD prices reflect our pricing review. They are validation proposals, not purchasable offers.
No checkout, subscription, trial billing or payment collection is enabled. Launch pricing, currency, taxes, billing intervals and plan limits must be confirmed before sale.
What counts as an application?
An application is one distinct product or service you operate as a unit. Its website, API, background workers and supporting services count together, including production, staging, development and preview environments.
One product using GitHub, Vercel, Supabase and Stripe counts as one application. Multiple repositories serving that product still count as one. A monorepo containing two independently operated products counts as two applications. Separate client websites count separately, even when they share a hosting account.
A provider connection is an authorized account or installation. It can serve several applications; linking the same connection or shared infrastructure to another application does not create another provider connection.
Under the proposed plans, only actively monitored applications use your application allowance. Archiving an application would stop collection and free its slot, while keeping existing history for the retention period included in your plan.
What counts toward a plan?
Free is proposed for one application and one user, with one non-revenue provider connection plus revenue connectors while annual recurring revenue (ARR) is below US$125,000. Revenue connectors and repository discovery do not consume the non-revenue connection allowance. At US$125,000 ARR or above, an upgrade to Founder, Studio or Team is required.
Paid plans include all available connector types. Connected-account limits, resource and endpoint allowances, refresh frequency, and member limits are still being defined; access to every connector type does not promise unlimited usage. Team requires a written application allowance, retention period, API budget, member allowance and support window before an offer can be made.
What if I need more capacity?
We propose including monitoring capacity in each plan, with optional fixed-price additions for needs such as more monitored endpoints, more frequent checks or longer history. Exact allowances and prices are still being evaluated.
Before any usage billing launches, you would be able to see your allowance and usage, receive advance limit notices, and choose whether to add capacity or upgrade. Any metered overages would require an explicit opt-in and a spending cap. Provider retries would not become surprise charges. No usage billing is enabled today.
What is available today?
The local review build includes application and resource inventory, on-device discovery, environment views and provenance. Live sync, historical storage, alerts, reports and team features listed in proposed plans are not implemented yet.
What happens if a provider is unavailable?
Marsward is designed to preserve context and label observations as missing or stale. Provider outages do not justify displaying invented measurements. Production availability commitments and support levels have not been established.