Developer tools
Flowstate Marsward
A dashboard for software projects, services, website health, and revenue.
- Category
- Developer tools
- Stage
- Beta
- For
- Software teams managing project infrastructure, monitoring, and subscription revenue.
About
Flowstate Marsward brings your software projects, services and website health into one dashboard. Explore mapped Stripe subscription revenue in our assisted pilot.
Features
- Problem
- Project context is fragmented across repositories and provider tools.
- How it works
- Connect an authorized GitHub repository to discover eligible provider references, then organize recognized or manually added resources by application and environment.
- Result
- Teams can keep services, owners, dashboard links, notes and runbooks together.
- Why
- Static discovery provides a starting inventory without claiming that detected code references prove live resources exist.
- Problem
- Teams need to understand potential operational impact across services.
- How it works
- Records dependency relationships between APIs, workers, frontends and infrastructure resources, including relationships across applications.
- Result
- Teams can inspect dependencies and potentially affected services from their inventory.
- Why
- The relationship view identifies where impact could spread without asserting incident cause or service failure.
- Problem
- Website availability is difficult to track alongside application context.
- How it works
- Runs scheduled checks against public HTTPS endpoints, recording HTTP results and response time; Vercel users can also read deployment information.
- Result
- Teams can see website health and deployment context alongside the application it supports.
- Why
- Monitoring is limited to endpoint availability and response time, rather than full page-load or server-resource monitoring.
- Problem
- Ongoing website issues can be missed.
- How it works
- Creates sustained endpoint incidents and sends configurable email notices for incidents and recovery.
- Result
- Teams receive signals when a monitored website problem persists or recovers.
- Why
- The product explicitly positions beta monitoring as context and notification support, not guaranteed emergency paging.
- Problem
- Revenue context is separate from operational views.
- How it works
- Offers an owner-only assisted Stripe pilot with mapped MRR snapshots and graphs.
- Result
- Eligible workspaces can view mapped subscription-revenue context with their application portfolio.
- Why
- Stripe setup is not self-service and requires assisted-setup availability.
Screenshots
