DocumentationOwn the whole
Own the whole
request lifetime.
Start with Web Standards, then add explicit ownership for child tasks, resources, disconnects, and shutdown.
Getting started
Create a Nelo application, run it with the Node adapter, and close it gracefully.
Open guide →Request ownership
Understand scopes, owned tasks, resources, and the boundary between handling and delivery.
Read concept →Cancellation
Propagate one typed reason through cooperative work without claiming forced termination.
Read concept →Resources
Register deterministic cleanup and preserve every failure during LIFO disposal.
Read concept →Nelo API
Routes, middleware, Fetch-style execution, and the portable application surface.
View API →Context API
Use params, JSON responses, owned tasks, request signals, and scoped resources.
View API →