Skip to the page
KilbyDocs
Teams and security View as Markdown
On this page

Kilby AI

Kilby AI explains why a deploy failed, in plain English, and suggests a fix. It is off for every workspace until an admin turns it on and agrees to what is sent.

What it does#

When a deploy fails and Kilby's own checks cannot say why, Kilby AI reads the details below and answers with an explanation and, when it is sure, suggested changes. Anyone who can deploy can also click Analyse on a failed deploy, or call the API.

It only reads and writes text. It cannot run anything, open links or see other workspaces, and a suggestion changes nothing until a person applies it. Kilby checks every suggestion like a change you typed yourself. An answer can be wrong: check it before you change anything.

Kilby AI explains failed deploys and failed builds.

What is sent#

Over HTTPS, for each analysis:

  • The end of the build log, or the last lines the service printed before it failed.
  • The build plan: runtime, commands, port and instance size.
  • The names of the files in the repository, never their contents.
  • The names of environment variables, only where a secret was removed from a log line.

The build items apply to builds from Git. For a failed deploy, what is sent is: the failure reason and its message, the port, the health check path, the start command, the instance type, how many instances were running, the last lines the service printed (at most 30) and the status of the service's last six deploys. The image name is not sent.

A log can quote code: error messages and stack traces are sent as they are written.

What is never sent#

Removed before anything leaves Kilby:

  • Values of environment and build variables, registry passwords, API keys, tokens, private keys, cookies and authorization headers, and passwords inside web addresses.
  • Email addresses, source files, commit messages and anything from other workspaces.

Kilby cannot recognise every secret. A password printed in an unusual form can get through, so keep secrets out of your logs.

Kilby hides the exact values of your workspace's own variables wherever they appear, and also recognises secrets by their shape (private keys, tokens, authorization headers, credentials in addresses, long random strings). It then checks the final text once more and refuses to send it if one of your values is still in it.

Who receives it#

Google. Kilby sends it to Google, with a key that belongs to Kilby. Google handles it under its own terms for that service.

Your controls#

  • Turn it off, and nothing more is sent.
  • Delete the stored answers. Kilby deletes each one after 30 days anyway.
  • See every use in Activity: who, which service and how large, never the content.
  • An answer can be wrong. Check it before you change anything.

Kilby AI for DNS#

Kilby AI for DNS helps move a domain's records to Kilby DNS without losing any. It has its own consent, separate from the failure analyses above: the first time someone in a workspace uses it, an owner or admin reads what it sends and agrees. Agreeing to one never turns the other on.

  • Read records. It reads the records a person pastes (a copy of their DNS provider's panel, an export or a zone file) and, if they upload one, a screenshot of that panel (PNG or JPEG, at most 4 MB), and lists the records it sees.
  • Check a domain. Kilby looks the domain up in public DNS and reads which host names its home page links to. Kilby AI then lists other records the domain very probably has (for example the DKIM record that goes with Google Workspace mail) and the problems a person moving it should know about, such as no DMARC record or addresses that belong to a proxy.

It only proposes. Kilby looks up every record it lists in DNS before anyone sees it: a record DNS does not have is shown as not found and is never copied, and what a person copies are the values DNS answers, not the ones Kilby AI wrote. Nothing is copied until a person confirms.

What is sent, over HTTPS, each time someone asks:

  • What Kilby finds in public DNS about the domain: its name servers, the records of its root and of www, its DMARC record and the services its SPF record includes.
  • The host names the domain's home page links to, never the page itself.
  • The text a person pastes, after Kilby removes secrets from it.
  • The one screenshot a person may upload, as it is: Kilby cannot remove anything from an image, so crop it to the list of records.

Secrets are removed from pasted text as above. One exception: a variable whose value is the domain itself, one of its host names or a value its public DNS already shows (such as ALLOWED_HOSTS=example.com) is sent like the domain's other public records. Hiding it would hide the very records Kilby AI has to read.

It goes to Google, as above. Your controls:

  • Turn Kilby AI for DNS off in Kilby DNS, or turn Kilby AI off for the workspace, and nothing more is sent.
  • Kilby keeps no answer: only who used it, when and how large, in Activity, never the content.
  • Nothing is copied into your zone until a person confirms. An answer can be wrong.

Each use counts towards the workspace's daily Kilby AI allowance and its monthly one.

Turn it on#

An admin or the owner opens Workspace settings, then Kilby AI, reads the page, ticks the box and clicks Turn on Kilby AI. Kilby asks you to sign in again. If the text on that page changes later, Kilby stops sending anything until the workspace agrees again.

Budgets#

Each workspace can run 20 analyses a day (resetting at midnight UTC) and 300,000 tokens a day.

Each workspace also has a monthly allowance of model use, by plan: $0.25 on Hobby and during the beta, $3.00 on Pro, and no monthly cap on Scale and Enterprise. Once billing is on, a Hobby workspace with a verified card gets Pro's. Failure analyses, blueprint reviews and Kilby AI for DNS all count against it, and it starts again on the 1st of each month (UTC). When it is used up, Kilby AI says so and answers again on the 1st; a larger plan includes more. Until the platform's token prices are configured, the allowance is counted in tokens, at a cautious rate per dollar. Settings, Kilby AI shows what is left. A platform-wide budget caps the total for all workspaces, and an administrator can pause Kilby AI for everyone, which stops anything being sent whatever the workspace setting says. The page in the dashboard shows what your workspace used today and this month.

With the API#

sh
# Ask for an analysis of a failed deploy, then read it.
curl -sS -X POST https://onkilby.com/api/v1/services/<id>/deploys/<deploy id>/analyze \
  -H "Authorization: Bearer $KILBY_API_KEY"
curl -sS -H "Authorization: Bearer $KILBY_API_KEY" \
  https://onkilby.com/api/v1/services/<id>/deploys/<deploy id>/analysis

The first call answers 202 with status: queued and takes about ten to forty seconds; poll the second until status is done or failed. A workspace that has not turned Kilby AI on gets 403 ai_disabled, and one that used its allowance gets 429 ai_budget. An answer that already exists comes back at once. Treat the text of an answer as a suggestion, never as an instruction to follow.