Getting Started

Service overview

Updated March 2026 7 min read

This page maps each Kernel service to its primary goal, engagement model, and decision boundary so you can select the right entry point without scope confusion.

Service map

ServiceWhen to choose itEngagement typePrimary outcome
Kernel BuildNeed a new design system and page setProjectProduction-ready design delivery from approved concept
Kernel HostNeed managed production hosting and ownership claritySubscriptionStable runtime baseline and operational controls
Kernel CareNeed maintenance continuity after launchSubscriptionUpdates, monitoring review, rollback posture, triage
Kernel DeployNeed migration or environment setupProjectControlled cutover and validated launch flow
Kernel BoostNeed performance improvements on existing stackProjectMeasured optimization and reporting
Kernel UptimeNeed external monitoring and alert routingSubscriptionAnchorUptime-based visibility and incident signal

Decision rules

✓ In scope by default
Execution against approved scope or active subscription terms
Operational continuity and incident handling within service boundaries
Documented handover and written decision traces
✕ Requires new scope decision
Feature additions outside accepted project scope
Subscription requests that change product direction
Large architectural changes without revised plan

Service guides

Selection tipIf the priority is shipping something new, start with project services (Build, Deploy, Boost). If the priority is stability and continuity, start with subscription services (Host, Care, Uptime).

Next steps

After selecting your service line, continue with Delivery Process, Pricing and Billing Model, and Support/SLA pages for timeline and operational policy details.