> For the complete documentation index, see [llms.txt](https://flowops.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://flowops.gitbook.io/docs/welcome-to-flowops.md).

# Welcome to flowOps

## Overview

FlowOps is a comprehensive incident monitoring and management tool designed to empower  non-technical users with proactive control over their services.With its intuitive interface and seamless integration with various cloud services and third-party SaaS tools, FlowOps provides real-time aggregation of status pages, enabling users to quickly identify and address service disruptions

The platform offers a feature flag control system that allows for easy rollback of deployments, maintenance notifications, and the ability to turn off or on specific features on the edge. This ensures efficient communication with customers about incidents and their impact on services, building and maintaining trust.

## Quick links

{% content-ref url="/pages/7dzTXBBcUWKSWarnauGw" %}
[Our Features](/docs/overview/our-features.md)
{% endcontent-ref %}

## Get Started

We've put together some helpful guides for you to get setup with our product quickly and easily.

{% content-ref url="/pages/8ccmjLBoc9gruYDSiMK1" %}
[Product Guides](/docs/product-guides/create-a-team.md)
{% endcontent-ref %}

{% content-ref url="/pages/OUmw4MSYw7bFGT49navn" %}
[Use Cases](/docs/use-cases/micro-saas-founders.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://flowops.gitbook.io/docs/welcome-to-flowops.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.