> For the complete documentation index, see [llms.txt](https://docs.sola.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sola.security/getting-started/overview.md). # Overview From hours to minutes ## Welcome to Sola! Sola is the **enterprise security brain**, a single, continuously updated understanding of your environment. Your team and your agents reason from it, instead of rebuilding context every time. Here, you ask the questions. Sola already has the answers. {% tabs %} {% tab title="Answer any security question" %} ![](https://633303660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMkiDTkdEK7CdyQX8KZZH%2Fuploads%2FI1gYKhh798LTxvI81V7M%2FSola-Logo_24_26%20\(1\).svg?alt=media\&token=4ebffa91-4da9-4296-8ae8-e5c75c148a13) From a quick lookup to a full blast-radius trace, every question deserves a real answer. Ask Sola anything, and get it back with the evidence behind it. {% endtab %} {% tab title="Give your agents a shared brain" %} ![](https://633303660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMkiDTkdEK7CdyQX8KZZH%2Fuploads%2FI1gYKhh798LTxvI81V7M%2FSola-Logo_24_26%20\(1\).svg?alt=media\&token=4ebffa91-4da9-4296-8ae8-e5c75c148a13) Homegrown agents keep rebuilding the same context from scratch, burning time and budget. With Sola, every agent queries the same governed brain instead. Nothing gets rebuilt twice. {% endtab %} {% tab title="Get a senior analyst, built in" %} ![](https://633303660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMkiDTkdEK7CdyQX8KZZH%2Fuploads%2FI1gYKhh798LTxvI81V7M%2FSola-Logo_24_26%20\(1\).svg?alt=media\&token=4ebffa91-4da9-4296-8ae8-e5c75c148a13) Even the best security teams can't watch everything, all the time. [Signals](#lumina-signals) is Sola's own pre-built agent, reasoning across your environment for risk and handing you the blast radius and recommended action already worked out. {% endtab %} {% endtabs %} ## How Sola works **Security-relevant data is scattered across your tools**, infrastructure, identities, business systems, and documents, and none of it talks to each other. Sola continuously reads across all of the data and resolves it into one connected model of your environment: every asset, every identity, how they relate, who owns what, and what's actually at stake. The key part happens before you ask anything. Instead of figuring out answers live, which gets slower and less reliable the more systems are involved, no matter how good the underlying model is, **Sola works it out ahead of time and keeps it current as your environment changes**. A question like "what can this identity actually reach?" is a lookup against an answer that already exists, not a fresh investigation assembled on the spot. **Every answer carries its evidence**, including what it's based on, and how confident Sola is. That's what makes it one brain rather than a lookup table, a shared, always-current, evidence-backed understanding that your team and your agents both reason from. {% embed url="" %} {% hint style="info" %} The 𝗦𝗼𝗹𝗮 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗕𝗿𝗮𝗶𝗻 maps your entire environment 𝗮𝗵𝗲𝗮𝗱 𝗼𝗳 𝘁𝗶𝗺𝗲. When a question lands, it already sees 𝗲𝘃𝗲𝗿𝘆𝘁𝗵𝗶𝗻𝗴 at once. Nothing gets skipped for lack of time. {% endhint %} ## How to use Sola Sola Lumina reasons from one shared understanding of your environment, always current and already resolved. Here's how to use it: * **Chat with the Sola AI assistant.** Ask questions directly, and get answers with reasoning and evidence. * **Connect your own agent,** built anywhere, on any stack, to query the brain via MCP. * **Build a custom agent inside Sola**, configured to your specific goals. * **Use Sola Signals**, Sola's own out-of-the-box agent, to surface risk proactively.

	Cover image
Sola AI Sola AI is Sola's built-in assistant, available in every Chat and Project. It reasons from the same understanding as everything else in Sola, the same brain your agents and Sola Signals draw from too.		Sola AI
Sola MCP Sola MCP connects an agent you've already built, wherever it lives, directly to that same understanding. It reasons from real context instead of gathering its own, from any AI-powered tool you already use.		Sola MCP
Sola Agents A Sola Agent is a custom agent you build inside Sola, with its own instructions, tools, and memory, configured to your team's specific workflows. It reasons from the same understanding as everything else in Sola. Nothing gets rebuilt from scratch.		Agents
Sola Signals Signals is Sola's own agent, pre-built and always on. Each day, it analyzes your entire connected environment and surfaces what matters most, with context, reasoning, and recommended actions already worked out, ready to act on.		Signals

## Projects and Chats Sola lets you create custom security solutions for your specific security use cases. **Projects and Chats are composed of 4 building blocks.** [**Queries**](/workspace/projects/queries.md) for data inquiry. Use queries to **create**, **view**, and **share data insights** that answer your cyber security questions. [**Canvases**](/workspace/projects/canvases.md) for data visualization. Create canvases to build **dashboards**, **reports**, and **interactive views** that display your insights and results in easy-to-understand **tables**, **charts**, and **graphs**. [**Alerts**](/workspace/projects/alerts.md) for monitoring and alert rules. Convert your important questions into alerts to **track security risks and get notified** when important events occur. [**Workflows**](/workspace/projects/workflows.md) for **automation** and **remediation**. Automate security actions to **respond faster and reduce manual effort**. ## Sola Signals [Sola Signals](/workspace/signals.md) is Sola's proactive intelligence layer. Every day, it analyzes your entire connected environment and surfaces a ranked feed of pre-investigated security risk signals, each with context, reasoning, blast radius, and recommended actions, ready to act on. ## Credit and usage types Sola uses **AI credits**, **workflow credits**, and **data records** for managing usage. **AI credits (copilot)** are the units Sola uses to represent actions completed by [Sola AI](/getting-started/sola-ai.md), including asking questions, generating canvases, creating workflows, or refining logic. Each credit represents an average AI interaction. Simple tasks use fewer credits, more complex tasks use more. *AI Credits refresh weekly.* **Workflow credits** represent AI usage for running [agentic workflows](/workspace/projects/workflows.md). Each credit represents a typical workflow execution across its steps. *Workflow credits refresh weekly.* **Data records** represent the data entries Sola processes from your connected [data tables](/integrations/data-sources.md#data-source-tables). Each row from a connected data source is counted as one data record. *Data record limits reset daily.* Sola plans offer varying allowances for AI credits, workflow credits, and data records. Higher tiers provide increased limits to meet your team’s usage and growth. {% hint style="info" %} **Credit resets**\ Credit allowances vary by plan and reset on schedule. Credits do not roll over. {% endhint %}

--- # 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://docs.sola.security/getting-started/overview.md?ask=&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.