Self-hosted Agents
Run Agents on your own infrastructure and keep its data and credentials in your environment.
- Who operates it
- Your team
- Current access
- Source available · pre-release
Discuss your work
Evaluate one job with a result you can check.
Tell us about an application you want to build or a job you want AI to handle. We will help you choose the product, deployment and next step.
Current access is shown in the product choices. System connections and delivery scope are confirmed before implementation.
Discuss implementation
Tell us what you want to do.
Describe the work and the result you need, then leave your email. Other information can follow later.
What happens next
- We read your request.
- We reply with questions or a self-service path.
- Before implementation, we agree on scope, fees and responsibilities.
We aim to reply within one business day.
Where it runs
Choose who operates your deployment.
Run Agents yourself, plan an enterprise deployment, or ask about Cloud hosting. Product access and operating responsibility are agreed separately.
Enterprise deployment
Plan deployment, integrations, backups and support inside an approved enterprise environment.
- Who operates it
- Responsibilities agreed with your team
- Current access
- Delivery scoped to the available product capabilities
Cloud hosting
A hosted delivery option for Awaken. Access, available capabilities and support must be confirmed before adoption.
- Who operates it
- AwakenWorks operates the platform
- Current access
- Hosted preview · access by agreement
Products and availability
Two products. Scope and availability agreed before delivery.
Source available · pre-release
Awaken Agents
Run the product independently or scope one Agent application inside an approved infrastructure boundary.
Preparation and implementation scope
- Bring
- An application you want to build or already operate, its first task, model and data needs, deployment constraints and technical contact.
- First decision
- A scoped 4–6 week implementation uses 2–4 release checks, including a permission decision and interruption-and-recovery path, to reach a go, change, or stop decision.
- Current boundary
- Further hardening, integrations, rollout, and support require a new bounded service scope on the same Agents foundation.
Preview access by request
Awaken Workforce
Connect business data and permitted actions, then coordinate one recurring job through human decisions and acceptance.
Preparation and implementation scope
- Bring
- One real job, its source system, responsible owner, human decisions, current manual effort, full cost, and acceptance condition.
- First decision
- Agree on the deliverables and released capabilities needed for one bounded paid validation, then make a go, change, or stop decision from the recorded result.
- Current boundary
- Request preview access, then confirm available capabilities, integrations, delivery and support for your scope.
Bounded paid validation
Agree on the work, measures, cost, and acceptance.
The standard validation covers one real application or recurring job, one approved environment, one integration, and 2–4 measures. The signed scope fixes the period, fees, responsibilities, and final decision.
- One application
- One application or recurring job in one approved environment
- One integration
- One standard system connection; additional systems require a scope change
- 2–4 checks
- Result quality, remaining human effort, full cost, and normal, approval, and recovery paths
- Go / change / stop
- A named acceptor makes the next decision from recorded evidence
What you receive
- A running end-to-end path
- An acceptance record against the agreed checks
- A risk list with operating and acceptance owners
- A final report and explicit next decision
Who owns what
- AwakenWorks
- Scope the target and boundaries, configure the agreed deployment and integration, run the normal, permission, and recovery paths, and record the result.
- Your team
- Provide the job, baseline, environment, restricted access, business rules, technical owner, decision maker, and final acceptor.
Production SLA, broad rollout, additional integrations, unlimited customization, and long-term operations are not included. They require a separate bounded scope on the same Agents foundation.
Before you start
What you need to know before contacting us.
Do I need an Agent already?
You can start with the work you want done. We will discuss suitable capabilities and setup; developers can create or connect an Agent through the existing Agents guides.
What should I prepare?
Describe one recurring job, the systems and information it uses, its responsible person and a result your team can check. Other details can follow after the first conversation.
How do we confirm which systems can be connected?
Describe your support, order or payment systems, the information needed and the actions to perform. We confirm the available integration scope, then agree on who handles setup, deployment and support.
How are costs agreed?
Software and model usage, infrastructure, system integration and implementation support are scoped separately. The systems, work frequency, deployment and deliverables shape the scope. We agree on fees and responsibilities before a paid implementation starts.
For solution providers and delivery teams
Use the same Agents foundation across customer projects. Agree on the customer-facing experience, integrations, delivery lead and support responsibility for each scope.
Discuss a delivery partnership