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

# Welcome to JamAI Base

> AI Platform for Secure, Controlled, and Rapid AI Solution Development and Deployment. AI made Insanely Simple!

Plug Large Language Models into Your Projects as Easily as Firebase—**No AI Stack Needed**.

* **Approach:** Introducing a serverless LLM native database featuring Generative Table. Begin your journey in minutes.
* **Advantage:** Bid farewell to the complexities and extra dependencies of platforms like LangChain or LlamaIndex. We simplify your workflow, so you can concentrate on creating amazing applications.
* **Key Feature:** Generative Table technology that transforms static database tables into dynamic, AI-enhanced entities capable of generating and interacting with data autonomously.
* **Application:** Ideal for developers seeking to rapidly deploy AI-powered features in web and mobile applications, enhancing user experience with minimal coding and reduced development time.

{% embed url="<https://www.jamaibase.com/_app/immutable/assets/Jamaibase.C2harmRl.mp4>" %}

{% hint style="info" %}
The name JamAI Base is derived from a blend of JamStack, AI, and Database, encapsulating its core functionality and target architecture.
{% endhint %}

## Core Concepts

#### Generative Table <a href="#generativetable" id="generativetable"></a>

* **Core Concept:** Foundational element of JamAIBase; all tables are types of Generative Tables.
* **Functionality:** Uses LLMs to autonomously generate and populate data based on application needs.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Action Table</strong></td><td>Facilitates real-time interactions between the application frontend and the LLM backend.</td><td>Ideal for orchestrating complex, multi-step LLM workflows with the simplicity of a spreadsheet.</td><td><a href="/using-the-platform/action-table.md">Action Table</a></td></tr><tr><td><strong>Chat Table</strong></td><td>Manages real-time multi-turn conversations for applications like chatbots.</td><td>Allows developers to create custom agent (GPTs) that combine instructions and extra knowledge.</td><td><a href="/using-the-platform/chat-table.md">Chat Table</a></td></tr><tr><td><strong>Knowledge Table</strong></td><td>Manages RAG data and structured metadata.</td><td><p></p><p><br>Serves as an "AI content management system."<br></p></td><td><a href="/using-the-platform/knowledge-table.md">Knowledge Table</a></td></tr></tbody></table>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jamaibase.com/get-started/readme.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 `build a script that syncs our docs to a CMS` 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.