Overview
Understand the Springbase ecosystem: Contexts, Chat, Recipes, Plans, Agents, Canvas, and the compounding loop that ties them together.
What Springbase Is
Springbase is a compounding knowledge engine for modern AI work. It connects your messy data, meetings, documents, apps, and research to high-end execution modes that can actually get work done.
Instead of starting from a blank prompt every time, you build a workspace where knowledge, workflows, and outputs improve each other over time.
The Compounding Loop
Every useful Springbase workflow follows the same loop: capture knowledge, ground the AI, execute work, and deliver a finished artifact.
| Stage | Action | Result |
|---|---|---|
| Capture | Record meetings, upload docs, or connect apps. | Raw knowledge enters the workspace. |
| Ground | Organize source material into Contexts. | AI answers become specific, cited, and business-aware. |
| Execute | Run Chat, Recipes, Plans, or Agents. | Springbase performs the actual work. |
| Deliver | Send output into Canvas, docs, code, tables, or connected apps. | Finished artifacts are ready to use, edit, share, or automate. |
The loop compounds because each useful source, prompt, Recipe, Plan, and output can become reusable infrastructure for the next task.
Core Execution Surfaces
Springbase gives you different ways to work depending on the job.
| Surface | Best for | Key feature |
|---|---|---|
| Chat | Quick questions, brainstorming, and flexible analysis. | Use frontier models and attach Contexts when answers need grounding. |
| Recipes | Repeatable, templated work. | Turn reliable prompts into reusable workflows with variables. |
| Plan Mode | Complex, multi-stage projects. | Break a large goal into editable steps, then execute them. |
| Agents | Hands-off automation across tools. | Use connected apps to take action, not just generate text. |
| Canvas | Editing and polishing outputs. | Keep documents, code, diagrams, and structured artifacts out of messy chat history. |
The Memory Layer: Contexts
Contexts are the brain of your Springbase workspace. They store the information that makes AI aware of your business, your customers, your meetings, and your internal knowledge.
| Source type | Examples | Use case |
|---|---|---|
| Files | PDFs, CSVs, Markdown, TXT, code, images. | Static research, policies, product docs, and technical references. |
| Meetings | Zoom, Google Meet, Teams, uploaded recordings. | Grounding answers in actual conversations, decisions, and follow-ups. |
| Live apps | Google Drive, Notion, GitHub, Slack. | Keeping knowledge fresh when source documents change often. |
| Web research | Search, crawled pages, market sources. | Pulling in current information for research and analysis workflows. |
The simplest mental model:
Sources -> Contexts -> Chat, Recipes, Plans, Agents -> Canvas or apps
Visibility And Collaboration
Springbase works for private solo workflows, team knowledge bases, and public community assets.
| Visibility | Who can see it | Typical use |
|---|---|---|
| Private | Only you. | Personal research, private notes, sensitive drafts. |
| Shared | Specific invited people or team members. | Team knowledge bases, internal workflows, collaborative docs. |
| Unlisted | Anyone with the direct link. | Lightweight sharing without public discovery. |
| Public | The Springbase community. | Reusable Contexts, templates, and assets others can discover. |
Use the narrowest visibility that still lets the right people get work done.
The Output Layer: Canvas
When Springbase creates something substantial, it should not disappear into a chat thread. Canvas gives important outputs a place to live, evolve, and be exported.
| Artifact type | What you can do | Examples |
|---|---|---|
| Documents | Edit, format, and export. | PRDs, briefs, reports, blog posts, proposals. |
| Code | Iterate, debug, and refine. | React components, scripts, HTML pages, prototypes. |
| Tables | Review and reuse structured data. | Competitive analysis, budgets, research matrices. |
| Diagrams | Visualize systems and flows. | Funnels, architectures, workflows, decision trees. |
How The Pieces Fit Together
You can use Springbase at three levels:
- Ask better questions. Use Chat with the right model and the right Context.
- Repeat reliable work. Save strong prompts as Recipes and reuse them with variables.
- Delegate bigger outcomes. Use Plan Mode and Agents when the job needs multiple steps or connected tools.
Why This Matters
Most AI tools make you repeatedly explain the same context. Springbase is designed so your knowledge, workflows, and outputs keep accumulating.
That means the second task should be easier than the first. The tenth should be faster than the second. Over time, your workspace becomes a system that remembers how your business works and helps move work forward.
Start Here
If you are new to Springbase:
- Read the Quickstart.
- Create your first Context.
- Ask Chat a question using that Context.
- Save one useful prompt as a Recipe.
- Try Plan Mode for a goal with multiple steps.
The fastest path is not to set up everything. It is to build one useful loop, then let it compound.
Related docs
Get from first chat to a grounded Springbase workflow in minutes.
Learn the core Springbase concepts: Contexts, retrieval, Recipes, Plans, Agents, Canvas, Meetings, permissions, and reusable assets.
Learn how to build living knowledge bases in Springbase with documents, notes, shared access, live sources, community Contexts, and grounded Chat.
Learn how to use Springbase Chat with Contexts, @mentions, shared knowledge, live sources, saved outputs, permissions, and practical prompt templates.