Skip to main content
Ordinary Next.js and SvelteKit apps use the maintained integrations described in deploy apps. A custom adapter emits one .amplify-hosting deployment specification with a default Node 22 or 24 compute resource. The Node major must match the compiler runtime; managed hosting uses Linux x64 (AWS deployment specification). The closed compute archive is limited to 220 MiB after trusted binding. Documents render through compute. Scripts and styles use immutable /releases/<BIJECTION_APP_RELEASE>/ URLs. The adapter installs the maintained browser application-state integration and creates a backend client for each request, preserving user identity and the release binding. Credentials remain server-owned; public browser configuration never contains runtime secrets. The deployment manifest may declare additional requirements:
Request rendering is required for every server artifact. Unknown requirements and shared persistent caching are refused before activation. Packaging compatibility does not establish hosted support for authentication, streaming, mutations or image optimization; those capabilities remain unverified through the provider. Provider targets, quota reservations, immutable branches, origin protection, resource retirement and the x64 builder image belong to installation operations.