Professional services
Implementation and onboarding
Service description: 14 July 2026
Engagement options
| Service | Typical scope | Commercial basis |
|---|---|---|
| Assisted evaluation | Evaluation planning, deployment assistance, use-case configuration, and findings review | $5,000; credited toward an annual license when purchased within 60 days |
| Standard remote onboarding | Single production deployment, baseline configuration, administrator enablement, and handover | $7,500 one-time |
| Professional remote onboarding | Scoped architecture, cluster deployment, identity, routing, policy, MCP, and operational readiness | Starting at $20,000 one-time |
| Additional remote services | Integration, migration, policy design, workshops, and operational assistance | $2,000 per consultant-day or $250 per hour |
| Onsite consulting | In-person workshops, deployment, validation, and production-readiness support | $2,500 per consultant-day; three-day minimum, plus expenses |
Pricing is a baseline and does not itself reserve dates or define a deliverable. The signed order form or statement of work (“SOW”) defines the actual scope, assumptions, schedule, fees, and acceptance criteria.
Implementation process
- Discover. Confirm outcomes, stakeholders, architecture, environments, identity, providers, MCP systems, controls, traffic, and target dates.
- Design. Agree the deployment topology, responsibility matrix, network flows, secret handling, policy model, observability, backup, and rollback approach.
- Prepare. The customer provisions infrastructure, DNS, TLS, backing services, access, provider accounts, change windows, and test applications.
- Deploy. Install the licensed release, configure required integrations, and record the as-built version and topology.
- Validate. Exercise authentication, routing, virtual keys, budgets, limits, guardrails, MCP permissions, audit evidence, failure paths, and recovery procedures in scope.
- Handover. Review operating procedures, open items, support routing, and customer acceptance; transfer day-to-day ownership to the designated customer team.
Remote onboarding
Remote work is performed through agreed conferencing and customer-approved access methods during the working sessions stated in the SOW. AethosHub may guide customer operators through changes or, where expressly authorized, perform limited changes in the customer environment. Remote onboarding normally includes kickoff, architecture confirmation, deployment guidance, baseline configuration, validation, an administrator walkthrough, and a closeout review.
Remote onboarding is not a managed service. After handover, the customer operates its environment and uses the purchased support plan for product questions and incidents.
Onsite services
Onsite work is subject to consultant availability, location, site-access requirements, visa and travel feasibility, and an executed SOW. Travel, lodging, visa costs, and local transportation are billed separately. International travel days are billed at 50% of the consultant-day rate. The customer must provide a safe workplace, required visitor approvals, working facilities, and timely access to the relevant personnel and systems.
Responsibilities
AethosHub responsibilities
- provide personnel with product knowledge appropriate to the agreed work;
- perform the tasks and deliver the artifacts expressly listed in the SOW;
- follow documented customer access and security procedures supplied before work begins;
- identify material blockers, risks, assumptions, and scope changes discovered during delivery; and
- handle customer confidential information under the applicable agreement.
Customer responsibilities
- appoint an empowered project owner and make architecture, security, platform, and application owners available;
- provide accurate requirements and make timely decisions, reviews, and approvals;
- provision and operate infrastructure, networks, DNS, TLS, databases, identity, backups, monitoring, and provider accounts unless the SOW expressly says otherwise;
- obtain internal change approvals and authorize all access to customer systems and data;
- maintain recoverable backups and a tested rollback path before production changes; and
- test and accept the configured solution against the agreed acceptance criteria.
Deliverables and acceptance
Depending on scope, deliverables may include an architecture decision record, deployment checklist, responsibility matrix, as-built summary, policy baseline, validation record, runbook, administrator workshop, and open-issues register. Product source code, generalized tools, pre-existing materials, and AethosHub know-how are not transferred unless a signed agreement expressly says so.
Acceptance criteria and review periods are defined in the SOW. If none are stated, the customer should identify a material non-conformity within five business days after delivery; AethosHub will use reasonable efforts to correct work that does not materially match the written scope. New requirements or environmental changes are handled through change control.
Security, data, and access
Customer credentials must not be sent by email or placed in tickets. Use customer-approved secret and access workflows. Access should be named, least-privilege, logged, and removed when the task ends. The customer decides whether production data may be used; AethosHub recommends synthetic or sanitized data for implementation and validation wherever feasible. See our Security pageand DPA.
Changes, dependencies, and scheduling
A delay in customer prerequisites or access may move scheduled work. Either party may request a written change when assumptions, scope, deliverables, timing, staffing, or dependencies change. AethosHub will describe the expected effect on fees and schedule before performing out-of-scope work. Cancellation and rescheduling terms are stated in the SOW or order form.
Start an engagement
Submit a quote request with the intended edition, deployment model, environments, identity provider, model providers, MCP scope, target timeline, remote or onsite preference, and any procurement or security-review deadline. For an evaluation, use Request an evaluation.