FRbext.dev

Build with bext

Guides and references for the Rust engine, PRISM applications, and the sites you run on bext Cloud.

Start with a task

Build a PRISM app

Start with a TSX page, then add routes and server-side data as you need them.

  1. Install bext

    Get the matched engine, compiler and framework release.

  2. Create your first site

    Set up the four starter files and run bext dev .

  3. Load real data

    Use a loader for reads and an action for form submissions.

Follow the quickstart
src/app/page.tsx
export default function Page() {
  return (
    <main>
      <h1>Hello, bext.</h1>
      <p>Your first PRISM page.</p>
    </main>
  );
}

Deploy with Cloud

Create a managed site, connect a verified domain, and follow deployments from your account.

  1. Choose a deployment path

    Provision WordPress, PrestaShop or PRISM, or use a configured Git project.

  2. Keep a recoverable archive

    Check the backup option, run history and private download links.

  3. Connect your assistant

    Use the Cloud MCP tools with a revocable account token.

Read the deployment guide
Read your Cloud projects
curl https://cloud.bext.dev/api/projects \
  -H "Authorization: Bearer $BEXT_CLOUD_TOKEN"

Keep your existing stack

Find the supported path for your current application before changing its production configuration.

  1. Move an nginx configuration

    Review compatibility, preflight checks and the takeover process.

  2. Find your framework

    Choose the adapter for your application and its runtime.

  3. Choose how to serve it

    Understand native rendering, proxying and deployment modes.

Plan an nginx migration
Framework migration guides
nginx     → /migration/from-nginx
Next.js   → /migration/from-nextjs
Express   → /migration/from-express
Vercel    → /migration/from-vercel

Find the failing layer

Start from the error you can observe, then check configuration, logs and request behavior.

  1. Check common failures

    Work through startup, routing, TLS and caching issues.

  2. Look up the error

    Find the meaning of an engine error and its next steps.

  3. Understand reloads

    Know when a source change, invalidation or upgrade is needed.

Open troubleshooting
Useful references
Startup and configuration → Troubleshooting
Unexpected response       → Request lifecycle
Stale content             → Invalidation & restarts
Service availability      → status.bext.dev

Common references

Keep these within reach.

Browse the documentation

Every topic, from your first route to the engine internals.

Need a hand?

Check service status, ask a question, or report a reproducible problem.

Find help & support
Search documentation

Start with a topic, a command, or a question.