What Applane is

Applane is a Chrome extension. A person on your team opens its side panel, describes an internal tool in plain words, and iterates with an AI agent until a working web app is deployed.

The app runs on Google Apps Script, inside your Google Workspace, under the account of whoever opens it. The model runs on Vertex AI in your own GCP project. Every Google call is made from the browser with the employee’s own token.

Applane’s backend stores your company’s configuration, the email addresses of the people who build, and your invoice. It never receives a Google access token, a line of app source, a prompt, or a row of your data.

Setting it up touches three places: the Google Admin console, one GCP project, and the Applane console. This site is split by who does each part.

Pick your role

Google Workspace adminChrome extension policy, Apps Script, accounts and groups, Drive sharing, offboarding.

GCP adminOne project with billing, five APIs, one IAM grant, an Internal consent screen and a web OAuth client.

Applane adminSign up, verify your domain, run the setup checker, manage seats and billing.

BuilderInstall the extension, sign in, build and share your first app.

For AI agents

Every page has a Copy as Markdown button next to its title, and is served as Markdown at the same path with a .md suffix (for example /gcp-admins/oauth-client.md). The whole site is at /llms.txt (an index, one line per page) and /llms-full.txt (every page in one file). Cache these files; re-fetch when the Last updated line or the ETag changes.

Before you start

• What runs where: one diagram of the three places Applane runs.
• Who does what: every step, who owns it, and how long it takes.
• The one-hour setup path: the order to do it in when one person has every right.