PanOS Documentation Hub
Comprehensive technical documentation for building, integrating, and extending PanOS in real-world environments
PanOS Documentation Hub
PanOS is a minimal Linux platform with a first-class JavaScript runtime, designed for fast boot, reproducible builds, and predictable integration in constrained environments.
This documentation set is intentionally large and technical. It includes:
- Build internals and boot flow
- Runtime architecture and process model
- Integration patterns for backend, frontend, edge, CI/CD, and embedded deployments
- System design playbooks and reference implementations
- Troubleshooting, optimization, and advanced customization
Fast Start
./0-install-deps.sh
./1-build.sh
./2-run.shIf this is your first time, read in this order:
Tracks
Core Platform
Kernel, rootfs, initramfs, build pipeline, and runtime lifecycle.
Runtime Internals
Deep architecture analysis, memory model, boot phases, and process behavior.
Node.js Development
Application creation, package strategy, and runtime best practices.
Integration Contexts
How to integrate PanOS in backend, frontend, edge, CI/CD, and embedded workflows.
Design Playbook
Practical architecture patterns and design examples for production systems.
Authoring with Fumadocs
How docs are integrated and rendered in this site using Fumadocs + MDX.
Complete Documentation Map
| Area | Document | Audience | Est. Time |
|---|---|---|---|
| Setup | 01-getting-started.mdx | New users | 8 min |
| Setup | 02-prerequisites.mdx | New users | 10 min |
| Setup | 03-installation.mdx | New users | 12 min |
| Core | 04-building.mdx | Builders | 20 min |
| Core | 05-running.mdx | Operators | 15 min |
| Core | 06-architecture.mdx | Advanced | 25 min |
| Dev | 07-nodejs-integration.mdx | JS developers | 20 min |
| Ops | 08-troubleshooting.mdx | All | 20 min |
| Delivery | 09-creating-iso.mdx | Platform engineers | 18 min |
| Advanced | 10-advanced.mdx | Power users | 30 min |
| Integration | 11-library-integration-contexts.mdx | System integrators | 28 min |
| Integration | 12-multi-context-recipes.mdx | Application teams | 32 min |
| Design | 13-system-design-playbook.mdx | Architects | 30 min |
| Reference | 14-reference-implementations.mdx | Engineers | 35 min |
| Docs | 15-fumadocs-authoring-guide.mdx | Maintainers | 18 min |
Integration Principles
When integrating PanOS as a runtime layer in larger systems, follow these principles:
- Define boundaries first: host responsibilities vs guest responsibilities.
- Treat boot as a contract: deterministic startup, stable device mappings, explicit kernel params.
- Make runtime state observable: expose health, logs, and version metadata.
- Design for failure domains: isolate build, boot, application, and transport failures.
- Prefer reproducible pipelines: pin kernel, BusyBox, Node.js, and package versions.
What Changed in This Documentation Generation
- Migrated docs rendering to Fumadocs + MDX for richer structure and maintainability.
- Added advanced integration context guides and design examples.
- Preserved the full technical corpus while expanding implementation-oriented recipes.
- Standardized English writing style for global contributors.
Next Recommended Read
Go to 11-library-integration-contexts.mdx if your main objective is integrating PanOS into real systems.