Show the source
Awaken is Apache-2.0. You can read the code, follow a decision, and propose a better one.
Reliability and openness
Teams need to see what happened, control what an Agent may do, and continue the same work after a restart or hand-off. These needs guide both the product and the way we describe it.
Each job needs a named owner and a result another person or system can recognize. An Agent may plan and act, but the owner decides whether the work is complete.
These rules guide product design and implementation support.
Awaken is Apache-2.0. You can read the code, follow a decision, and propose a better one.
Run the control plane on infrastructure you choose. Keep Session records and credentials inside that operating boundary.
Choose providers and execution backends explicitly. Open protocols and readable formats make later changes easier, though never free.
We distinguish what is available now, what is still a preview, and what remains a target. When a limit matters to your decision, we state it near the claim instead of hiding it in a footnote.
Read the current implementation boundariesUse these maintained pages for source, licensing, website data handling, private deployment, or a security concern. Product availability and limits are stated beside the relevant path.
Open the exact Awaken revision used by the current public documentation.
Read the Apache-2.0 license attached to that source revision.
See what the public website and opportunity form collect and where it goes.
See the current way to evaluate Agents in an approved environment.
Send a private report or ask which disclosure path applies.
Ask about a design, report an unclear limit, or submit a change through the links below.
Ask a question or propose a change where others can examine it.
Start with a bounded change and its acceptance conditions.
Follow the repository path from a clone to a reviewed change.
Read the unresolved trade-offs and comment on the decision.