Build a site
Install the amw compiler, create a starter, and publish the ordinary site and its second experience.
AMOOSEDWEB / DEVELOPER DOCUMENTATION / v0.27.1
Build AmoosedWeb into your product.
Technical documentation for third-party developers. Compile and host a carrier-backed site, read verified resources from native C++, Node.js, or .NET, and use the current native C/C++ Reader preview.
CHOOSE A PATH
What do you want to do?
Read a site from an app
Use the published Node.js or .NET Reader to list and download verified resources.
Install a Reader →Use native C or C++
Download the Windows x64 Reader ZIP with prebuilt libraries, headers, CMake targets, and examples.
Get the native SDK →Understand the format
See how files carry the second experience and which bytes the Reader verifies.
Read the illustrated guide →MINIMAL WORKFLOW
From starter to verified output.
Install the compiler, create a project, edit site/ and app/, then build. The generated project includes its own README and version-matched helper scripts.
npm install -g amoosedweb-compiler
amw init my-site
cd my-site
build.cmd # Windows
# sh build.sh # macOS or LinuxFor an existing host, export the same-version runtime and follow its route contract. Validate the live host after publishing.
amw export-runtime ./amw-routes
amw check-host https://your-site.example/BOUNDARIES
Know what the verification proves.
Integrity
Readers verify carrier parts and reconstructed resources against the index. HTTPS authenticates the transport.
Format details →Access
A public hosted index is discoverable. External index and member keys are transferable bearer credentials.
Access model →Deployment
Carriers need byte-preserving hosting. The app runtime and its service worker belong on the same origin as the site.
Host contract →Building with an AI coding agent? Give it the SDK integration guidelines for agents →.
PROTOCOL
See the bytes and the read path.
The illustrated protocol guide explains the AMW payload, carrier layouts, index and member keys, resource checks, and same-origin boot flow. Start there for a human-readable map; use the full format specification for exact fields and limits.