Meet Vibrant

Turn thought into something real.

A new AI workspace for exploring ideas, working with context, and shaping useful outputs.

PreviewWorkspace capabilities are in preview.

Ask VibrantLive model

Ask anything.
Free, no sign-up.

Talk to the Vibrant model right here. Explore an idea, get a concept explained or work through a piece of code.

What Vibrant is for

  1. Explore with context

    Start from the notes and files you already have, not a blank prompt.

    Preview
  2. Shape useful outputs

    Move from a conversation to a document, table or code you can keep.

    Preview
  3. Keep work connected

    Conversations, sources and drafts stay together in one space.

    Preview

The workspace

Conversation on one side. Real work on the other.

Ask a question, attach what matters, and watch it become a draft you can edit. Pick a scenario below to see how a session is structured.

Assumption Lab

Concept preview

See what changes when the assumptions do.

A small planning model you can adjust. Change an input and the numbers, the map and the chart update together — the kind of back-and-forth Vibrant is designed around.

An interface concept with simple arithmetic. It is not a Vibrant benchmark or a measure of infrastructure performance.

Capabilities

Four building blocks, each with its real status.

Status labels come from one configuration file, so this page never claims more than the product does.

Conversation

Preview

Think out loud with a model that keeps up with follow-ups, corrections and changes of direction.

  • Follow-up questions
  • Edit and retry
  • Readable history

Project context

Preview

Attach files and notes to a space so the work starts from what you know — and see which sources are in use.

  • Files and notes per space
  • Visible sources
  • Remove what no longer fits
  • Artifacts

    Shape answers into documents, tables and code you can edit, copy and keep.

    Preview
  • Connected tools

    Bring in the services your work already lives in, with a clear permission at each step.

    Planned

Developers

Developer access — planned

Predictable, structured output.

We are designing developer access around responses with a clear shape. There is no public API, SDK or endpoint yet — this section shows the direction, not a product you can call.

Illustrative schemaExample only. Not a live API response.
{
  "type": "artifact",
  "format": "document",
  "title": "Repair café — first look",
  "status": "draft",
  "sources": [
    {
      "id": "src_1",
      "name": "repair-cafe-notes.md"
    },
    {
      "id": "src_2",
      "name": "volunteer-survey.csv"
    }
  ],
  "sections": [
    {
      "heading": "What we already have",
      "source_ids": [
        "src_1",
        "src_2"
      ]
    },
    {
      "heading": "Open questions",
      "items": [
        "Insurance for the venue",
        "Tool storage"
      ]
    }
  ]
}

How we build

Principles you can check us on.

  1. You stay in control

    Vibrant proposes; you decide. Drafts stay drafts until you accept, edit or discard them.

  2. Context stays visible

    You can see which files and notes shaped a response, and remove them when they no longer belong.

  3. Status is stated plainly

    Every capability carries its real state — available, preview or planned. Nothing is presented as finished before it is.

Bring a thought. Leave with something real.

Vibrant is in early access. Tell us how you would use it.