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

# Welcome to Open SaaS

This guide is designed to **help you understand, install, and build with Open SaaS** even if you're new to full-stack development.

We’ll walk you through everything from:

* Installing the starter kit locally
* Exploring key features like authentication and payments
* Understanding how Open SaaS uses Wasp, Stripe, OpenAI, and more
* Deploying your SaaS app to the web
* Troubleshooting common issues

#### 📚 Who is this for?

This guide is great for:

* Developers building their first SaaS product
* Makers launching a micro-SaaS MVP
* Indie hackers testing startup ideas
* Curious learners exploring the Wasp framework

#### 🛠️ What You’ll Need

Before you start, you should be comfortable using a terminal and have these installed:

* Node.js (v18+)
* Git
* A code editor (like VS Code)

We’ll take care of the rest together


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.learndevtools.blog/getting-started/welcome-to-open-saas.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.