Infrastructure

This page covers the basics behind the Playbooks infrastructure and why it sits at the core of the product. It is what allows us to host a wide range of projects in a secure, meaningful, and affordable way.

Overview

At Playbooks, we built a proprietary runtime that can host anything from a small primitive like a component to a more complex project like a stateful application.

Key Tenets

  • on demand execution
  • serverless runtime behavior
  • secure, sandboxed environments
  • shared infrastructure with load-balanced demo traffic
  • ephemeral execution with caching after successful boots

How It Works

  • We fetch the source code from GitHub or another connected project source.
  • We prepare it for deployment using either your configuration or AI-generated defaults.
  • We boot the play inside an isolated runtime environment.
  • If the demo runs, the environment is cached and made available for future boots.
  • If the demo fails, the play is temporarily removed from the marketplace until it is fixed.

Your Sandbox

Each play is allocated it's own sandbox that's optimized for fast, clean boots where execution state is never written to persistent disk.

  • Plays run inside a base environment optimized for Playbooks.
  • Plays run using Docker-compatible configuration.
  • Each sandbox is isolated and secure.
  • Sandboxes are given hard limits on compute, memory, and disk.
  • The runtime is ephemeral by design.

At a high level, this gives developers a reliable place to present working software on-demand without needing to manage the hosting layer themselves.

Resources

Resources are limited at the moment and subject to change.

  • 2 vCPUs
  • 4GB memory
  • 4GB disk
  • 1GB shared memory

Debugging

  • built-in logs
  • browser-based shell access
  • runtime stats and operational visibility
  • tools that help you understand whether a demo is healthy and behaving as expected

For a deeper dive, see Demos.

Environment Variables

  • account-level environment variables can be shared across projects
  • project-level environment variables can override account defaults
  • variables are injected at runtime rather than shipped with the downloadable source

Private Files

  • account-level private files can be reused across projects
  • project-level private files can override account defaults
  • private files are mounted at runtime and stripped from the distributed code

Collectively, this infrastructure is what allows Playbooks to present software as something live, testable, and ready to evaluate rather than just another repository link.

PrevQuickstartNextArtificial intelligence