Build and ship.
From draft to live App, hosted by Kylon.
Agents change an App on a draft with its own preview and its own copy of the data. A person who can edit the room publishes it, and Kylon hosts the source, the database and the live App.
Every change starts as a draft.
Source in git, hosted by Kylon
Each custom App's source lives in a git repository Kylon hosts. Ask an agent for a change and it works on a draft branch; the live version is never edited in place.
A preview for every push
Every push to a draft builds a preview of that exact commit. You open it from the draft link the agent posts, or from the Drafts menu on the App.
Its own copy of the data
An App with a database gives each draft a copy of it, taken from production when the draft starts. What you enter in a preview stays there.
Private while in progress
A preview opens only for signed-in people who can read the App's room, even when the live App is public.
A person decides when it goes live.
Publish from the draft
When a preview is ready, people with write access to the App's room see a Publish button on the draft. Nobody else does.
Choose who can see it
Publishing asks who the App is for: room members, everyone in the workspace, or anyone with the link.
Exactly what you reviewed
Publishing ships the commit behind the preview you looked at, runs any pending database changes once and closes the draft. A draft that has fallen behind the live App has to catch up first.
Agents ask first
When an agent publishes, a person with write access to the room approves on a card: this once, for 24 hours, or always for that App. Standing approval covers one App and one agent, and lapses if the App's visibility or its Automations change.
People publish directly
A person who presses Publish only confirms, and can let the agent publish that App without asking, for 24 hours or until they revoke it.
Each App keeps its own data.
One database per App
An App that stores data gets its own Postgres database with its own login. No other App's login can connect to it.
Schema changes ship with the code
A custom App changes its tables through numbered migration files committed with its source. They run on the draft's copy when pushed and on production when published, each one once.
Records without source code
Database Apps have no source code behind them: people browse and add records in the Data Viewer.
One file tree, every version kept.
Three kinds of folder
Shared files everyone in the workspace can read, a folder for each room that its members can open, and each agent's own folder, readable by the people who can use that agent.
Every save is a version
Saving a file adds a new version instead of replacing the old one. Ask an agent to bring back an earlier version and it becomes the current one again.
Read-only inside the sandbox
In an agent's cloud computer the files are mounted read-only. Changes go back through Kylon, where permissions are checked.
What you see
A Files tab in every room, and a Knowledge page for the files the whole workspace shares.
Your App, at your address.
Add a hostname
People with write access to the room add a hostname such as app.example.com in the App's settings, and agents can do the same.
Kylon lists the DNS records
You add the records Kylon shows at your DNS provider. The status reads Pending DNS setup until they check out, then Active, and the App is served over HTTPS at your domain.
The default address stays
The App's kylon.app address keeps working. Each App has one custom domain, and each domain points at one App.
On the surface
A draft link in the thread, a preview to click through, and a Publish button for the people who can edit the room.
Tools an agent built live on someone's laptop, change in place with no preview, and nobody can say which version is live.
Every change has a draft and a preview, and going live is a person's decision.
Good
questions.
Do I need my own git or hosting?
No. Kylon hosts each custom App's source, previews, database and live version. Agents work on the source; people never need to touch git.
Who can publish an App?
People with write access to the App's room, from the Publish button on a ready draft. When an agent publishes, one of them approves on a card first, unless they gave that agent standing approval for the App.
Can I go back to an earlier release?
Yes. Someone with write access to the App's room can roll back from the Kylon CLI. The app itself has no rollback button.
Can a Database App be public?
No. A Database App can be shared with room members or the whole workspace. Custom Apps can also be opened to anyone with the link.