Customer-hosted
Your customer provides the host and connects their Temporal service. Fleetnook brings deployment approvals, health and usage into one operating view.
Bring your own cloud ↗Run agents in your customer’s cloud. Deploy approved images, monitor health and track usage from one shared console.
Customer-hosted today. Fleetnook-managed hosting is coming later. Open Fleetnook to see your sign-in options.
01 Runs where your customer runs
02 Connects outbound
03 Measures what matters
04 Customer stays in control
The same approval path, with the Temporal service your customer chooses.
Deployment requests
Customer decisions
Health & reported usage
Local credentials & signing key
Approved image & resource limits
Workflow history in this environment
The customer supplies the host and Docker. Agent dependencies have their own network access.
Workflow history outside the customer environment
Self-hosted Temporal can keep workflow history inside the customer environment. The agent runs on the customer’s host.
This is the planned operating model, not an available deployment option. Today, bring your own cloud or connect an existing Linux host.
Bring your own cloudA deployment crosses the boundary only with customer approval. Health and usage bring the operating picture back.

Every customer environment brings its own network, credentials and operating rules. Fleetnook gives your team a repeatable path to deploy and support agents without asking customers to give up control.
Follow the deployment pathApprove an immutable image, enroll the customer-side runner, and keep deployment state visible from request through readiness.
Read the install guideTrack runtime health, resource use and reported usage. Stale data stays visibly stale. Workflow payloads are outside the telemetry protocol.
Explore the operations viewCustomers approve deployments and can grant or revoke time-limited diagnostic access. Support sessions are not enabled yet.
See how control worksFleetnook keeps the handoff simple and the operating picture connected.
View the runner guideShare an immutable image reference with your customer and distribute the signed Fleetnook runner bundle.
A small runner connects to Fleetnook over HTTPS from inside the customer environment.
The customer reviews the requested image and resource limits before the runner starts it.
Health and approved usage telemetry flow back. The agent runs locally; workflow history and model calls follow the customer-configured services.
Fleetnook connects the operating layer while the customer keeps their own runtime, Temporal endpoint and local credentials.
Allow-listed health, resource measurements and usage counters reported by the customer runner.
Agent containers run in the customer environment. Workflow history is stored by the Temporal service the customer chooses.
Deployment requests and fixed diagnostic access. Interactive support access is planned and will require separate consent for each session.
Connect a self-hosted cluster or Temporal Cloud namespace. Managed Temporal hosting is on the roadmap.
Fleetnook works with containerized Temporal workers. Bring your image, your namespace and your customer’s deployment requirements.
Read the getting started guide# check the verified runner and host
node fleetnook-runtime.mjs doctor https://fleetnook.com
# enroll this environment
node fleetnook-runtime.mjs enroll https://fleetnook.com
# start the supervised runtime
node fleetnook-runtime.mjs runThe customer-side runner starts the approved image in the customer’s Docker environment. Fleetnook hosts the control plane and dashboard. Fleetnook-managed compute is planned; the current product does not host customer agent containers.
Yes. Connect Temporal Cloud or a self-hosted Temporal endpoint. Connection credentials are configured locally for the customer runtime.
Fleetnook’s telemetry protocol is designed for allow-listed health and usage fields. Workflow history is held by the Temporal service you configure. Your agent and its dependencies may have separate network data flows, so review those before deployment.
No interactive support session is available today. Customers can approve time-limited diagnostic access. Interactive access is planned with a separate customer consent step before each session.
Track reported token and workflow usage against customer-approved rates, review charge estimates and issue statements. Export the figures for reconciliation with your billing workflow. Payment collection is separate.
See the operations console or start with the customer runner guide.