All pages
Every published page by section, with its availability and evidence.
Accounts
8 pages
Start here
- Beyond Accounts
One Beyond account signs you in to Workspace, CDN and Delegate. Start here to get in, recover access, manage organizations or end your sessions.
- Availability: Experimental
- Evidence: Read from source
- Explanation
Get into your account
- Sign in and create an account
Sign in with GitHub, Google or an email address and password, create an account, and return to the product that sent you to Beyond Accounts.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
- Confirm your email
Finish an account you created with an email address by opening the confirmation link, and know what to do when the link no longer works.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
- Recover access to your account
Set a new password with a one-time recovery link when you cannot sign in, and understand what happens to your sessions afterwards.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
Manage your account and organizations
- Profile, language and sign-in methods
Change your name, language and appearance, and add or remove the ways you sign in to your Beyond account, with the rules that protect it.
- Availability: Experimental
- Evidence: Read from source
- How-to guide
- Organizations, members, roles and invitations
Create an organization, invite people with a one-time link, accept an invitation, change roles, remove members and hand over ownership in Beyond Accounts.
- Availability: Experimental
- Evidence: Read from source
- How-to guide
- Sessions and signing out
See where you are signed in, sign out of this device or of everything, and learn what Beyond products do when your session ends or your account is suspended.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
Fix a problem
- Accounts troubleshooting
Every message Beyond Accounts shows when something goes wrong, what it means, what was and was not changed, and the safe next step.
- Availability: Experimental
- Evidence: Read from source
- Reference
Delegate
10 pages
Start here
- Beyond Delegate
Beyond Delegate turns a request written in your own words into approved, planned and delivered work done by external AI agents, with a person deciding at every gate.
- Availability: Experimental
- Evidence: Read from source
- Explanation
- Get started with Delegate
Reach Beyond Delegate, sign in through your Beyond account, and find your workspace, your projects and the decisions that are waiting for you.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
Work with other people
- Workspace and collaboration
Invite people to a Delegate workspace, understand seats and the plan, choose roles, grant access per project, and know what each role can and cannot do.
- Availability: Experimental
- Evidence: Read from source
- How-to guide
From request to result
- Requests
Write a request in your own words, import one from another system, answer the questions of the analysis, edit without losing the original text, and refer to it as R-1.
- Availability: Experimental
- Evidence: Read from source
- How-to guide
- Review and planning
Evaluate a proposed requirement, approve it or return it with a reason, refine it, set priorities, and plan, order and approve a release before any agent starts work.
- Availability: Experimental
- Evidence: Read from source
- How-to guide
- External work with agents
Launch development with an external agent, follow its activity, answer its blockers, review and accept or return its results, and authorize correction work.
- Availability: Experimental
- Evidence: Read from source
- How-to guide
- Versions and delivery status
Create a version from a finished release, request a test deployment, read its status and evidence, accept or reject the test, and understand what production approval does and does not do.
- Availability: Experimental
- Evidence: Read from source
- How-to guide
- Notifications and communication
How Delegate tells you that something is waiting, which messages it never sends, and what the operator-only Communication screen reads and does not do.
- Availability: Planned
- Evidence: Read from source
- Explanation
Fix a problem
- Recover from a problem in Delegate
What to do when your Delegate session ends, Beyond Accounts is unreachable, an action is refused, a record changed under you, or an external outcome is unknown, without losing work or repeating an action.
- Availability: Experimental
- Evidence: Read from source
- How-to guide
- Supported limits in Delegate
The limits Delegate enforces today and the capabilities it does not have, in one place, each with the message you see when you reach it.
- Availability: Experimental
- Evidence: Read from source
- Reference
Workspace
18 pages
Start here
- Beyond Workspace and Projects
Beyond Projects keeps your organizations, their members and your projects in one place, and opens a project in Workspace, Delegate or CDN. Development in Workspace is closed and is granted by Beyond.
- Availability: Experimental
- Evidence: Recorded run
- Explanation
- Sign in to Beyond Projects
Sign in to Beyond Projects with your Beyond account, choose the organization you are working in, and read the three parts of the screen.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
- Closed access to Workspace development
Development in Workspace is closed. Beyond enables it for an organization and selects each member individually, and both are needed. What the three states on your screen mean and what does not give access.
- Availability: Experimental
- Evidence: Recorded run
- Explanation
Organizations and projects
- Organizations and members
Beyond Projects shows your organizations and your role. Creating an organization, inviting people and managing members happen in Beyond Accounts, and you come back to Projects when you are done.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
- Create a project from the Beyond template
Create a project in Beyond Projects from a template version you choose. The version is recorded with the project, and the project receives the identity that Workspace, Delegate and CDN share.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
- Register an existing project
Give work that already exists in Delegate or CDN one project identity in Beyond Projects, without a template, without development access and without changing anything in those products.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
- Open a project in Workspace, Delegate or CDN
A project has one entry for each product. Each entry takes you there with the project in context, and the product checks your access when you arrive.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
- Rename, archive, restore and delete a project
What each project action in Beyond Projects does, who can use it, and what it never does. Archiving and deleting remove nothing in Workspace, Delegate or CDN.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
Develop in Workspace
- Open a project in Workspace
Arrive in Beyond Workspace from Projects, sign in, understand each way of not getting in, and start, stop and come back to your own development environment of the project.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
- Edit files in Workspace
Open files in tabs, let autosave write them or save at once, know what saved means, resolve a conflict when Codex or someone else changed the file, and keep unsaved drafts across devices.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
- Work with Codex in Workspace
Start a personal conversation, steer or interrupt a run, understand the one running conversation per environment, connect your own provider account and read usage. Running Codex inside an environment has not been validated.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
- Review and integrate changes
Read the three numbers of your working copy, make a checkpoint, bring in what others integrated, review the diff, the verification and the conflicts, and integrate. Integration is not publication, and there is no Publish action.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
- Preview your work and share it
See the preview of your environment, choose who can see it, create and revoke visitor links, and know what a visitor can and cannot do. A stopped environment has no preview, and nobody starts it by looking.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
- Packages, modules and what you develop
Read the packages and public modules Workspace detected, see which build, choose explicitly what is in development, and create files, modules and packages with the assistants. Page, widget and layout assistants are not available.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
- Workspace on a phone
What Workspace offers on a phone or a small touch screen. You read conversations and the review, edit text with the same save and conflict rules, and compare with a linear diff. The full desktop editor is not loaded there.
- Availability: Experimental
- Evidence: Recorded run
- Explanation
- The Workspace desktop app
What the Workspace desktop app is, how it differs from Workspace in a browser, and what has and has not been run. It was only smoke-run and has never been used for a real sign-in.
- Availability: Experimental
- Evidence: Recorded run
- Explanation
With the other products
- Use Delegate with a Beyond project
Link a Delegate workspace to a Beyond organization, arrive from Beyond Projects and attach a repository, adopt a project Delegate already has, and understand each refusal. These screens exist only in a Delegate installation that is connected to Beyond Projects.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
Fix a problem
- Troubleshooting Beyond Projects
Start from what Beyond Projects or Workspace shows you. You cannot create a project, you have no development access, Projects cannot answer, someone changed the project, your environment did not start, the preview is unavailable, another conversation is running, or your changes conflict.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
Developers
12 pages
Start here
- Develop with Beyond
How a Beyond project is organized for a developer. A workspace lists packages, a package publishes public modules, and modules reach each other only by bare specifier. What you can run today, and what you cannot.
- Availability: Experimental
- Evidence: Recorded run
- Explanation
- The project template
What a project created from the beyond-web template 0.1.0 contains, how to serve and preview it with the Beyond command line, what template.json records, and the limits of this template version.
- Availability: Experimental
- Evidence: Recorded run
- Reference
Packages and modules
- Packages and public modules
How a package publishes a module in a project created from the beyond-web template, how to add a public module and a sibling package whose bare import is preserved, and how to check each change.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
- Your first UI
Build a web page from one public module declared by a module.json, with its own stylesheet, a declared SVG asset and source maps; serve it with the Beyond command line, see it in a browser, change its CSS without reloading, and request its production output.
- Availability: Experimental
- Evidence: Recorded run
- Tutorial
- Styles
How the stylesheets of a public module are compiled and delivered by Beyond Packages: CSS and SCSS with partials and a theme, Tailwind scanning only the sources a module declares, selecting another module's stylesheet with .css, the shared global stylesheet of a package, what a failed stylesheet does, and how a change reaches a page.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
- Author a Beyond widget
Build a React 19 widget declared by its module.json, give it a Tailwind stylesheet and a styled public dependency of another package, see it mount in its own shadow root, change its code and its CSS without reloading, and do the same with a Vue or a Svelte view.
- Availability: Experimental
- Evidence: Recorded run
- Tutorial
Extend Beyond
- Integrate a view framework
What a widget controller does for a view framework, shown by a widget written without one, in plain HTML, with a client controller and a server controller; then how the supplied React 19, Vue and Svelte adapters do the same, and what a new adapter must own.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
- Embed a widget in an existing page
Put a Beyond widget into a page that was not built with Beyond, from another origin, with the same dependency and shared styles it has in its own application: the import map, the registration, two instances, and what happens on removal and reinsertion.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
- Create a modular execution environment
What a host that executes Beyond public modules must do, shown by BEE Node and Deno: resolving bare identities through a development service or a release's resolution, a Node host that renders widgets on the server, the difference between packaged and composed artifacts, and what a host may and may not expect from updates.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
- Create a bundler or a processor
The two ways to teach Beyond Packages a new way of compiling a public module, shown with the bundlers it ships: a bundler written against the core module contract, a bundler composed from processors with the SDK, and a reusable processor with its inputs, outputs, diagnostics, dependencies and cleanup.
- Availability: Experimental
- Evidence: Recorded run
- Tutorial
Test your code
- Test a package
Write ordinary test files for a Beyond package and run them with beyond test, Node's own test runner over the compiled public modules; locate a failure in the TypeScript source, narrow a run, mock a public module, assert asynchronous behavior, read coverage on the sources and attach a debugger.
- Availability: Experimental
- Evidence: Recorded run
- Tutorial
- The beyond test reference
The exact contract of beyond test: the command line, how test files are collected, what the test processes receive, the build gate, module mocks, coverage, the file identities of served modules, the module manifest override, the messages and the exit codes.
- Availability: Experimental
- Evidence: Recorded run
- Reference
CDN
39 pages
Start here
- Beyond CDN
What the Beyond CDN prepares and delivers, how its three stages work, what a GET request can never do, and what is outside version 1.
- Availability: Experimental
- Evidence: Read from source
- Explanation
- Quickstart
Request one prepared public module from a local development server and from the CDN with a single client, changing only the base origin.
- Availability: Experimental
- Evidence: Read from source
- Tutorial
Delivery
- Delivery reference
The HTTP contract for retrieving compiled public modules, styles, source maps, assets and resolution documents, identical on a development server and on the CDN.
- Availability: Experimental
- Evidence: Read from source
- Reference
- URLs and identities
The path grammar of a compiled public module, the sources an identity names (registries, Git repositories and archive digests), and the rule that lets one relative URL work on every origin.
- Availability: Experimental
- Evidence: Read from source
- Reference
- Request options
Every query option of a module, style or map request, with its values and defaults, and what happens when a value is invalid or not produced.
- Availability: Experimental
- Evidence: Read from source
- Reference
- Outputs, styles and assets
The four resource families of a package version (modules, styles, maps and assets), how an import selects the JavaScript or the stylesheet of a public module, the shared stylesheet of a package, and how companions are advertised.
- Availability: Experimental
- Evidence: Read from source
- Reference
- Strategies per environment
One resolution and delivery model, consumed four ways: browsers with native ES modules or SystemJS, Node.js through BEE Node and Deno through its import map, with the development updates that work in all of them and the local measurements behind the defaults.
- Availability: Experimental
- Evidence: Recorded run
- Explanation
- Native ESM and import maps
Load published modules in a browser with native ES modules: the release shell with its inline import map and preloaded eager modules, or an import map you build from a resolution document.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
- SystemJS
The system loader mode of an application: System.register outputs loaded by SystemJS 6.15.1, which each release stores as its own loader.js, and how to load the same outputs from a page of your own.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
- Resolution
The beyond-resolution/1 document and the import map every origin answers at /resolution.json and /importmap.json, mapping each public specifier to an origin-relative URL, with scopes for coexisting versions.
- Availability: Experimental
- Evidence: Reproduced run
- Reference
- Caching and releases
ETags and conditional requests, the development and published cache policies, and why an exact version URL can be cached as immutable.
- Availability: Experimental
- Evidence: Read from source
- Reference
- Private access
How a member or a guest opens a private application: the exchange on the application's host, the host-only access cookie, short resource grants, the two access errors and what privacy cannot hide.
- Availability: Experimental
- Evidence: Read from source
- Reference
- Errors
Every error code of the delivery contract with its status, meaning and the right reaction, including the miss that never starts a build and the service-level answers.
- Availability: Experimental
- Evidence: Read from source
- Reference
- Retrieving the outputs of a release
What a release holds after preparation, the three places one output can be retrieved from, and the authorized management path that answers a member before the application has an address.
- Availability: Experimental
- Evidence: Read from source
- Reference
Management
- Management reference
The authenticated API that registers applications, runs the three preparation stages, and manages releases, domains, access, plans and quotas.
- Availability: Planned
- Evidence: Read from source
- Reference
- Authentication and conventions
Conventions of the management API: bearer authentication, roles and capabilities, idempotent mutations, pagination and the error envelope.
- Availability: Planned
- Evidence: Read from source
- Reference
- Applications and targets
Create and change applications, choose their visibility, loader mode and source map policy, define their frontend and backend targets, and bind an application to a Beyond project.
- Availability: Planned
- Evidence: Read from source
- Reference
- Registration and the pinned graph
Stage 1. Register dependency selections and let the CDN pin the complete package and version graph from metadata, then review graphs, diffs and update notices.
- Availability: Planned
- Evidence: Read from source
- Reference
- Preparation and inventory
Stages 2 and 3. Prepare a candidate release from a pinned registration, inspect the inventory of what is reachable, and understand readiness.
- Availability: Planned
- Evidence: Read from source
- Reference
- Jobs
Durable jobs of the three stages: states, stage progress, queue position, turns and limits, cancellation, retries, logs and failure codes.
- Availability: Planned
- Evidence: Read from source
- Reference
- Releases, promotion and rollback
Immutable releases and their states, binding the production and testing environments with a compare-and-set, rolling back to a retained release, and retiring.
- Availability: Planned
- Evidence: Read from source
- Reference
- Domains
Reserve the single free testing subdomain of an application, add custom domains and verify their ownership with a DNS TXT record.
- Availability: Planned
- Evidence: Read from source
- Reference
- Access and guests
Read the access policy of an application, invite external guests with expiring application-scoped grants, and revoke them.
- Availability: Planned
- Evidence: Read from source
- Reference
- Plans, credit and usage
Read the plan and entitlements of an organization, its credit balance and ledger, its measured usage by category, and join the premium waitlist.
- Availability: Planned
- Evidence: Read from source
- Reference
- Quotas
The configurable limits on packages and bytes per application and organization, how logical use is counted, and what happens when a limit is reached.
- Availability: Planned
- Evidence: Read from source
- Reference
Realtime
- Realtime reference
Follow preparation while it runs: private channels, persisted events with sequences, snapshots, replay after a reconnect, and revocation.
- Availability: Planned
- Evidence: Read from source
- Reference
- Channels and grants
The three private channel levels, and the short-lived grant a member obtains to join them.
- Availability: Planned
- Evidence: Read from source
- Reference
- Events
The event envelope, the microbatch a broadcast message carries, and every event type with its channel, stage and delivery class.
- Availability: Planned
- Evidence: Read from source
- Reference
- Reconnect and replay
Recover the exact state of a channel after a gap, a reconnect or a closed tab, using a snapshot, a cursor and persisted events.
- Availability: Planned
- Evidence: Read from source
- How-to guide
- Revocation
What happens to an open subscription when a session ends, a membership changes or a grant is revoked, and how a client should react.
- Availability: Planned
- Evidence: Read from source
- Explanation
Guides
- Guides
Task guides for the CDN: the two ways to publish a Beyond package to npm, ordinary npm dependencies, backend targets, one URL for local and CDN, and troubleshooting.
- Availability: Planned
- Evidence: Confirmed direction
- Explanation
- Publish Beyond source to npm
Publish a package as Beyond source so that the CDN recognizes it and compiles its public modules through Packages.
- Availability: Planned
- Evidence: Read from source
- How-to guide
- Publish a precompiled distribution
Compile your package before publishing and declare it as a distribution, so that the CDN delivers your outputs instead of compiling your sources.
- Availability: Planned
- Evidence: Read from source
- How-to guide
- Use ordinary npm packages and React
Depend on packages that know nothing about Beyond, such as React, and understand how peers, versions and unsupported inputs are handled.
- Availability: Planned
- Evidence: Recorded run
- How-to guide
- Widgets and view frameworks
How Beyond widgets written with React 19, Vue, Svelte or plain HTML are prepared and delivered by the CDN: packages compiled by the bundler they declare, framework controllers, styles adopted inside each widget's shadow root, and the shared stylesheet of a package.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
- Backend targets
Prepare a backend target, read its artifact closure and frozen resolution, and run it in an environment of your own. The CDN never runs it.
- Availability: Planned
- Evidence: Read from source
- How-to guide
- Same URL, local and CDN
Write a consumer once and point it at a local Dev Server or at the CDN by changing a single base origin, and know the differences you must expect.
- Availability: Experimental
- Evidence: Read from source
- How-to guide
- Troubleshooting
Start from the symptom: a module answers 404, a release never becomes ready, a job waits or stops, access is refused, or events stop arriving.
- Availability: Planned
- Evidence: Read from source
- How-to guide
- The applications of a Beyond project
Arrive in CDN administration from Beyond Projects, register an application for the project, add an application that already exists, read the Project panel of an application and release it from its project.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
Concepts
7 pages
Shared concepts
- Shared concepts
One canonical explanation of each idea that Beyond products share, so the product guides can link here instead of defining it again.
- Availability: Experimental
- Evidence: Read from source
- Explanation
- Account, organization and product workspace
A Beyond account is one person, an organization is a group of accounts, and a product workspace is where a product keeps its own people and permissions. None of them implies another.
- Availability: Experimental
- Evidence: Read from source
- Explanation
- Identity and resource permissions
Beyond Accounts decides who you are and which organizations you belong to. Each product decides what you may do with its own resources. This page says who decides what.
- Availability: Experimental
- Evidence: Read from source
- Explanation
- Sessions and single sign-on across products
You sign in once at Beyond Accounts and every product recognizes you. This page explains the two kinds of session, what travels between products, and what ends when.
- Availability: Experimental
- Evidence: Recorded run
- Explanation
- Request, approval, dispatch and verified completion
Four words that Beyond never uses for one another. Asking for something, deciding it, sending it to a provider and seeing it verifiably finished are separate records.
- Availability: Experimental
- Evidence: Read from source
- Explanation
- Project, organization and account
An account is one person, an organization is a group of accounts, and a project is one stable identity that an organization owns and that Workspace, Delegate and CDN share. A project is not a repository, a package or an application.
- Availability: Experimental
- Evidence: Recorded run
- Explanation
- Preview, integration and publication are different things
A preview is your running environment that others may be allowed to see. Integration merges your branch into the shared branch of the project. Publication is neither, and it is not part of Projects or Workspace.
- Availability: Experimental
- Evidence: Recorded run
- Explanation
Troubleshooting
1 pages
Start from a symptom
- Troubleshooting
Start from what you see. Each symptom leads to the one page that holds its fix, in Accounts, Delegate or the CDN.
- Availability: Experimental
- Evidence: Read from source
- How-to guide