How can I try Takibi Base before using my own workspace?

Takibi Base offers a sample workspace you can explore without signing up for anything. You can browse how documents are organized, change Profile access settings, and run questions through the CLI against sample data. The catch: any edits you make in the demo reset when you refresh the page, and anything that touches real storage — uploads, imports, downloads, and billing — requires your own workspace.

What you can try in the sample workspace

The demo is built to let you see the core mechanics of Takibi Base before committing to a workspace. According to the site, you can:

• Browse document organization — see how files sit inside projects and folders, and how Takibi converts them to Markdown for agent search.
• Change Profile access — open a Profile's Access tab, choose Edit, and select which folders it can read. This is the same permission model you'd use in production.
• Ask a question via the CLI — run a query and see the response format: matching passages, citations, and an evidence support score.

The CLI example on the site shows what a real response looks like:

$ takibi ask -q "What is our refund policy?" --json
{
  "spans": [{
    "text": "Customers may request a refund within 30 days of purchase.",
    "documentId": "00000000-0000-4000-8000-000000000010",
    "documentName": "refunds.md",
    "chunkId": "00000000-0000-4000-8000-000000000090",
    "title": "Eligibility"
  }],
  "citations": [{ ... }],
  "support": 0.4,
  "supportVersion": "v1",
  "abstained": false,
  "candidateCount": 1,
  "answerability": "unknown",
  "conflict": false
}

Each returned span includes the exact passage text plus a citation (document ID, document name, chunk ID, title). The support field is a measure of how well the retrieved evidence backs the answer — in this example, 0.40 on version v1 of the scoring.

What resets when you refresh

The demo is explicitly non-persistent. The site states that demo changes reset when you refresh, and that edits reset on refresh. So you can experiment freely with:

• Changing folder access on a Profile
• Modifying document organization
• Running different CLI queries

None of it carries over. Treat the sample workspace as a sandbox for understanding the workflow, not as a place to set up real configuration.

What requires your own workspace

Four operations are gated behind a personal workspace, per the site:

If your goal is to test whether Takibi handles your actual document types, or to verify that your files convert correctly to Markdown, you'll need to create a workspace. The demo only shows the interface and query mechanics against sample data.

Checking plans and pricing

There's a pricing page at takibase.com/pricing for workspace plans. The site doesn't publish specific pricing details in the material available here, so check that page directly for current numbers. Billing is one of the operations that requires your own workspace, so you won't encounter payment flows in the demo.

A practical way to evaluate it

1. Start in the sample workspace. Run the CLI query example, change a Profile's folder access, and look at how documents are indexed (the site mentions statuses like indexed, converting, and quarantined).
2. Note what you'd need to test with real data. If your evaluation depends on uploading your own files or checking conversion quality, plan to create a workspace.
3. Check the pricing page before creating a workspace so you know what you're signing up for.
4. Export format — the site mentions exporting a project in Open Knowledge Format (OKF). If that matters to your workflow, verify it works in your own workspace, since exports likely fall under the download restriction.

The demo is enough to decide whether the Profile-based access model and cited-passage response format fit how you want your agents to retrieve information. It isn't enough to validate document conversion on your own corpus — that step needs a workspace.