About Kona

Business work that keeps its reasoning.

Learn why Kona Business AI combines direct business analysis with a persistent workspace for sources, assumptions, scenarios, previews, and editable deliverables.

Public resource

Written for people, search engines, and agents. Product boundaries are stated directly so this page can be used without JavaScript.

What to know

Clear guidance, current boundaries.

These details describe the current public product. Review the linked capability and policy pages before making a consequential decision.

01

Why Kona exists

Business work often begins with an ambiguous question and ends in a document, model, presentation, decision, or operating plan. Between those points, teams search across sources, debate assumptions, redo calculations, and lose the reasoning that made an answer credible. Kona Business AI is built to keep that chain together so a result is easier to inspect, improve, and explain.

The aim is practical: help a founder or operator move from a question to reviewable work without pretending that generated output is automatically correct. Kona makes room for evidence, uncertainty, calculations, versions, previews, and human approval instead of hiding the work behind a polished paragraph.

02

Chat and Workspace

Chat is for a direct answer, focused analysis, research synthesis, or a bounded deliverable. Workspace is for persistent, multi-step work that benefits from a brief, uploaded files, approved sources, explicit assumptions, deterministic scenarios, generated items, and continued editing. Build and code capabilities live inside Workspace so the user does not have to restart the project in a disconnected surface.

Both modes are designed around the same principle: the preview and usable result should be more prominent than the interface around it. Generated documents, spreadsheets, presentations, images, and interactive code should be reviewed in context and exported when a durable copy is needed.

03

What responsible use means

Kona can make mistakes, and source material can be incomplete or hostile. People should verify consequential claims, assumptions, citations, formulas, forecasts, legal language, and customer-facing work before acting. External resources and connected data are treated as evidence rather than authority, and instructions embedded in that content should not override the user’s request or the product’s safety boundaries.

Kona is not a substitute for legal, tax, medical, investment, or other regulated professional advice. The public capability, trust, privacy, and developer pages state current boundaries so customers and agents can understand what is supported before they rely on it.