Built from betrayal, aimed at utility

Make the exit ramp before the platform gets worse.

Kairos is live. The core loop — search, synthesize, cite — shipped in one afternoon on a slow machine in East Tennessee. This is the first honest shape of a Manitec AI product: stable, respectful of your workflow, and not interested in renting you back the habits you already built.

AccessibleSearch-firstLive now
  • Core loop shipped: web search, answer synthesis, and cited sources — working end to end.
  • Next focus: file upload, image upload, document-grounded answers, and persistent session context.
  • Business posture: not anti-Perplexity cosplay, but a cleaner tool made for people who got stranded by tier games.

Product frame

Who it is for

People who use AI as infrastructure, not entertainment. They research, upload, compare, pull context across documents, and hate having key workflow features moved behind a higher wall after adoption.

Primary user

Solo builders, researchers, indie operators, and obsessive note-workers who need one place to ask, upload, and synthesize.

Core emotional job

Restore trust. The product should feel stable, legible, and respectful of dependence rather than eager to exploit it.

Competitive edge

Philosophy-grounded product choices: humane limits, transparent scope, and no pretending convenience is generosity when it's really extraction.

Version one

MVP feature set

The core loop is done. Now we build the rest of the workflow layer — the parts that make Kairos genuinely irreplaceable for daily use.

Shipped ✅

  • Web search with source links and answer synthesis.
  • Groq-powered response generation with citations.
  • Clean Next.js UI deployed on Vercel.
  • Repo live at Manitec-HQ/kairos on GitHub.

Building next 🔜

  • File upload for PDFs, docs, and plain text context.
  • Image upload for visual question answering.
  • Persistent project threads or session memory.
  • Shareable answer pages or exportable notes.
  • Custom domain.

System design

Technical shape

Use what already fits your hands. Reuse proven patterns from current Manitec work where it saves time, but do not inherit baggage just because it exists.

Front end

Next.js 15 app with a search-first interface, cited answer rendering, and upload tray coming next.

Retrieval layer

Tavily API for web search. One clean provider, one clear path. No over-engineered federation before day one works.

Model layer

Groq for speed and cost efficiency. Room later for route-by-task logic as the product matures.

Ship rhythm

Build path

Small, mean, useful. The kind of roadmap that gets built instead of admired.

Days 1–3 ✅

Core loop — shipped

Single thread UI, Tavily search, Groq answer synthesis, cited source rendering. Working end to end and live on Vercel.

Up next

Document context

Parse uploaded files, chunk them, ground answers against file context, and expose which file influenced the answer.

Following

Image and sharing

Add image upload flow, visual Q and A, and a clean answer share page or export function.

Then

Public beta shell

Custom domain, tightened UI, homepage language, and open access to trusted early users.

Public note

This product exists because an extremely useful tool taught us two things at once: what modern AI workflow should feel like, and how quickly that trust can be spent. So yes — thank you for the inspiration. And no — users should not have to rent back the habits they already built.

Immediate next moves

What to build next

The core loop is live. Now we make it irreplaceable.

1. Custom domain

Point a real domain at Kairos. Something clean that lives under the Manitec brand or stands alone.

2. File upload

PDF, doc, and plain text support. Ground answers in your own documents, not just the web.

3. Session memory

Persistent threads so the conversation doesn't die on refresh. Real workflow tool behavior.