> For the complete documentation index, see [llms.txt](https://docs.electrik.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.electrik.dev/hello-electrik/hello-electrik.md). # Hello Electrik Your next big SaaS starts here! ## What is Electrik? Electrik is an open-source Laravel starter kit for your next big SaaS. It's 100% open source and you can use it for commercial purposes ## Why another Laravel starter kit? It's true that there are some fantastic starter kits available out there. Some of them are offically supported by Laravel itself. My primary reason behind creating this starter kit is to provide all the essential nuts and bolts required to create a base for a solid SaaS application. Also, I am an avid fan of open source. And it hurts me to see that almost all other starter kits have some or the other features locked as premium features and they ask for paid subscriptions. This is why I have built Electrik. It has everything that you need to start your next SaaS project, right from user management to subscription billing! And I plan to keep it open source. I am also planning to make it a sponsor-ware, where you are not bound by subscription plans or one-time payments. If you want to sponsor this project, you are most welcome. If not, you are still most welcome :smile: ## What features does Electrik provide? Here is a non-exhaustive list of features you get out of the box: * User management * Team management * Subscription Billing via Stripe * Notifications alerts * Banners * Roles and Permissions Management * and much more --- # 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.electrik.dev/hello-electrik/hello-electrik.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.