Hosted services

Hosted services are processes Dorky operates outside an individual machine. They can create a machine, hold the provider credentials required to provision it, and connect an account to a bounded inference allowance. The machine still runs the services and routes declared in its Dorkyfile.

The statuses below describe the current product. A service used by Dorky's own fleet is not yet a public self-service product unless the section says so.

Availability

Service	Status
Managed provisioning	Built for Dorky's fleet. Customer self-service is in progress.
Accounts and prepaid inference	In development. The complete customer flow is not available yet.
Device approval	Planned. Not available yet.
Wildcard request provisioning	Foundations built. Request-time provisioning is not available yet.
Scheduled runs	Design in progress. Not available yet.
Hosted operation and support	Direction being defined. No service-level commitment is published.

Managed provisioning

Status: Built for Dorky's fleet. Customer self-service is in progress.

The provisioner service accepts an authenticated request carrying a grant for one substrate. It checks the grant and the configured quotas, calls the substrate provider, and returns the new machine's address. The substrate credential stays on the provisioner service. A machine asking for another machine never receives that credential.

This path has been driven end to end inside Dorky's fleet: one machine asked its agent to provision, the request passed through the provisioner service, and the new machine started behind a closed door. The customer CLI path is still being connected to accounts and provision grants. Until that work is complete, a customer may still need a direct substrate integration for dorky apply.

Accounts and prepaid inference

Status: In development. Not available yet as a complete customer flow.

The accounting service can create a durable account, start a Stripe test-mode Checkout, verify a signed Stripe webhook, record prepaid credits, and issue a bounded inference allowance. Current integration work connects that service to passkey sign-in, an exhausted trial allowance, and a return to the same machine after Checkout.

The first product in this path is prepaid inference credit for an existing machine. Node rent, pause enforcement, live Stripe activation, and routes that charge another caller remain separate unfinished work.

Planned hosted services

Device approval

Status: Planned. Not available yet.

The planned flow sends a typed authorization request to an enrolled owner device. The device signs an allow or deny answer, and the system records the request and its result. A standalone prototype has proven the push-and-sign exchange. The on-machine inbox, device enrollment, receipts, and the finished phone surface remain to be built.

Wildcard request provisioning

Status: Foundations built. Request-time provisioning is not available yet.

Dorky already has a managed wildcard edge and a provisioner service, but they operate as separate parts. The planned path authenticates a request before allocating a machine, maps the requested hostname to a declared template, provisions one machine for that name, and routes later requests to the same machine. Customer-domain authentication and traffic routing are still open design and implementation work.

Scheduled runs

Status: Design in progress. Not available yet.

The planned pattern puts the clock in a hosted, always-on, or customer-operated scheduler service. That service wakes a sleeping machine through a scoped route and records acknowledgements, heartbeats, retries, and a terminal receipt. The target machine remains free to sleep between runs.

The current Dorkyfile has no schedule stanza, and the kernel has no cron service. The first scheduler is being designed as a replaceable userland service that uses the existing service, secret, and route declarations.

Hosted operation

Status: Direction being defined.

Dorky currently operates the managed public edge and the provisioner used by its fleet. Open decisions define what additional value belongs in the hosted network, what remains entirely on a machine, how a machine can leave that network, and which runtime components become open.

There is currently no published support channel, support tier, or service-level commitment. Those items should not be inferred from the existence of the managed edge or provisioner.