Nerddi ID identity
The control plane uses Nerddi ID for user authentication. Authorization keys off immutable account subjects and internal workspace membership—not mutable email addresses.
SECURITY
Hosted code should never own the cloud.
Nerddi Cloud is designed around explicit trust boundaries instead of treating uploaded project files as trusted application code.
Cloud / Host separation
User management lives in Cloud. Site serving and immutable artifacts live in Host. Privileged mutations are sent through signed, replay-resistant internal requests.
Untrusted uploads
Uploads are validated for paths, file policy, archive behavior, MIME type and resource limits before a deployment can be published.
No arbitrary server execution in v1
The launch platform serves static/client-side projects. Arbitrary PHP, shell, Python, CGI and server configuration are blocked until isolated runtimes exist.
Immutable releases
Published files are versioned by deployment. A rollback changes the active version rather than rewriting deployment history.
Auditability
Security-sensitive actions emit audit events for account, site, deployment and operator activity, while user-facing errors suppress database paths and internal exception details.
Request and abuse controls
OAuth, control-plane mutations, partner API calls and the signed Cloud-to-Host API have bounded request sizes and rate controls. Public abuse intake has an independent privacy-preserving submission limit.
Malware scanning hook
Host can integrate ClamAV during deployment finalization. Scanner availability and results are recorded honestly; Nerddi Cloud does not claim antivirus coverage when the engine is not configured.