Structured builds for apps that need more than packaging.
PyCompiler ARK centralizes project context, build locking, plugin-driven pre-build logic, and CLI or GUI workflows in one coherent toolchain.
What it does well
Designed for projects where consistency, extensibility, and explicit build contracts matter.
Normalized build context
Engine input is flattened into a single contract, so every interface consumes the same project state.
Internal module apply
`init --apply-internal` can prefill `build.include` for internal project modules with confirmation or `-y`.
Lock-based rebuilds
Lock files preserve the build environment and make rebuilds deterministic across machines.
BCASL pipeline
Use plugins for validation, preparation, and cleanup before the build engine is invoked.
Interface preview
A fast glance at the current workspace experience.
How it fits together
Each layer stays focused: the workspace defines the contract, engines consume it, and plugins prepare it.
1. Initialize
Create the workspace, normalize the configuration, and decide what should be included or excluded.
2. Prepare
Let BCASL plugins and dependency analysis prepare the project before the build engine runs.
3. Build
Run a selected engine with the same data contract whether you are in CLI or GUI mode.
Documentation
Jump straight to the guides that describe the contracts and extension points.
Global config
Project metadata, build include/exclude rules, and workspace defaults.
Read the guide →Create an engine
Build and register a compiler engine using the engine SDK contract.
Read the guide →CLI reference
Explore the command-line interface for workspace and build operations.
Read the guide →About
PyCompiler ARK is an open-source build workshop for Python projects. It keeps the project state, build logic, and extension points explicit instead of hiding them behind opaque automation.
Source
Everything lives on GitHub, and the site is intentionally lightweight so it can act as a project front door rather than a marketing shell.
Open the repository →