---
title: How Kite Works
description: What Kite does on its own in Slack, what it does when you ask, how it decides when to check with you, where the website editor fits, and how credits are used.
---

# How Kite Works

Kite is your AI marketer in Slack. It researches your business, builds a growth strategy, and ships the work that brings you new customers. Most AIs wait for instructions. Kite finds what needs doing and does it. Here are the core ideas that make everything else in these docs make sense.

## What Kite does on its own

- **Offers work when it arrives.** The moment Kite joins a channel it reads your website and offers one or two pieces of work it can start on.
- **Watches your team's conversations.** Every hour Kite scans the Slack channels it is in for new messages from your team, matches them against your active initiatives, and posts a digest of the moves worth making (at most three digests a day).
- **Reports back.** When Kite finishes a task it posts the result in the thread where the work was asked for.
- **Runs what you schedule.** Teams can set up recurring or webhook-triggered workflows, for example a weekly conversion check. See [Initiatives, reports, and workflows](/capabilities/initiatives-reports-and-workflows).

## What Kite does when you ask

Everything else starts with a request in a thread, a direct message, or an email to your team's `teamslug@kite.space` address: research a competitor, draft a comparison page, build a landing page, write an email sequence, pull a prospect list, audit the site for conversion problems. Kite does the work and posts the result. See [What Kite can do](/capabilities/).

## How Kite decides when to check with you

Each team has an autonomy setting. The default, **propose first**, tells Kite to propose and wait before anything that changes public messaging, spends money, or affects legal standing, revenue, or customer retention. Routine, reversible work it just does and reports. The alternative, **act first**, tells Kite to act on clear next steps and then report what it did. Telling Kite to publish or send in chat is the OK. See **[Approvals and autonomy](/slack/approvals)**.

## Slack and the browser editor

Kite has two main places where you work with it. You can also email Kite. See [Ways to work with Kite](/get-started/ways-to-use-kite).

- **Slack** is where Kite brings you research, drafts, digests, and results, and where you reply to keep things moving.
- **The browser workspace** is where you make hands-on changes to your website (describe an edit in chat or click an element to change it, preview, publish), browse integrations, read analytics and leads, and manage billing. See **[Website Building](/website-building)**.

When Kite drafts a website change from Slack, the card it posts has a **Preview** button to see the draft and a **Review** button that opens the editor, where you merge and publish.

## Draft versus live

In the website editor there are two versions of your site:

- **Draft and preview**: what you see as you work. Edits appear here right away.
- **Live (published)**: what your visitors see on the web.

Changes reach visitors when they are published. If your live site looks out of date, the change has not been published yet. See **[My changes aren't showing](/publishing/changes-not-showing)**.

## Your web address

Every published site gets a free `your-site.kite.space` address, which you can rename from the publish panel. On the Growth or Business plan (or during the trial) you can connect your own domain. See **[Publishing](/publishing/)** and **[Custom domains](/custom-domains/)**.

## Credits

Every conversation you have with Kite and every task it runs uses **credits**. One credit is one US dollar of usage. Research, drafting, site edits, and retries all draw from the same pool. Bigger or more complex work uses more. See **[How credits work](/pricing-credits/how-credits-work)**.

## Undo and version history

Kite saves a version of your site after each change. You can preview any version and restore to it. See **[Undo changes & version history](/troubleshooting/version-history)**.

## When something goes wrong

If a preview will not start or a chat turn gets stuck, it is usually quick to recover. Start with **[Troubleshooting](/troubleshooting/)**.

## Keep exploring

- **[Working with Kite in Slack](/slack/)**
- **[What Kite can do](/capabilities/)**
- **[Website Building](/website-building)**
- **[Plans, Pricing & Credits](/pricing-credits/)**
