ProxyLang Overview
ProxyLang is a human-readable, indentation-based language for defining whole applications — pages, data, commerce, state machines, and agents — in a single .pxy file that ProxyCore runs. No braces, no boilerplate: the file you read is the system that runs.
A whole site, in one file
Blocks nest by indentation. A site names the app; a page declares a route and its content; a machine adds governed behavior. Here is a complete, runnable file:
site "ProxyWeb Demo" direction: modern-minimal page Home: route: / heading: ProxyCore, served from one .pxy paragraph: This whole site is defined in a single ProxyLang file. callout success: Parsed once at startup; served as cached bytes. machine Turnstile states: locked open when coin: state = open unlock gate
What you can define
site / pageRouted, pre-rendered pages in the Brevet design system.machine / thingChecked state machines, driven live and audited per action.schema / queries / mutationsA fixed data contract — the only reads and writes allowed.formTyped inputs that run a pre-declared mutation on submit.bars / line / tableCharts and tables filled from SQL per request, no JavaScript.commerceA catalog and checkout with an audited order lifecycle.agentGoverned orchestration — a model picks from allowlisted actions.Why indentation, not braces
The surface is deliberately small and reviewable. Capability — what data a form can write, which actions an agent may take, which transitions a machine allows — is declared in the text, so reading the file tells you the system's blast radius. That review property is the point.
Start here
- Getting started — write and run your first
.pxy. - Language reference — every block, with real syntax.
- Examples — a storefront, a dashboard, a guestbook, an agent.
Status
ProxyLang is in preview and private dogfooding — not yet released for general external use. The blocks shown run on the proxyweb runtime today, but names and details may still change. Reach out to evaluate early.