> For the complete documentation index, see [llms.txt](https://docs.friggframework.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.friggframework.org/0.2/roadmap/page-1.md). # Overview {% embed url="" %} We've got a dedicated roadmap tool to help you track specifics, and to let you make suggestions. Wherever you're comfortable, since it's integrated to GitHub. At a very high level, however, here's what we want to accomplish in the near, mid, and long terms: ### Near Term Roadmap This is in the next 3-6 months, heading into 2023. * Rapidly add more API Modules * Add unit tests to all core modules to harden them up for future iteration * Simplify the install process * Add more documentation * Add notes for deploying using popular services ### Mid Term Roadmap In the next 6-12 months, through 2023 * Add support for major databases * Postgres * Redis * MySQL ? * DynamoDB * Add support for all major cloud providers * Google Cloud * Microsoft Azure * Add CLI for rapidly adding integrations * Add robust versioning system * Analytics and Management API and corresponding code ### Long Term Roadmap Sometime in the future, end state goal * Make Frigg easily deployable with docker/kubernetes if desired * Support multiple languages for runtime * Optimize the primitives so Frigg is the fastest possible service * --- # 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.friggframework.org/0.2/roadmap/page-1.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.