ADEPLOYMENT
One approved image.
A repeatable install.
Approve an immutable image, enroll the customer-side runner, and keep deployment state visible from request through readiness.
Read the install guide Early access · built for Temporal teams
Your agents.
Their infrastructure.
Ship the agent you built into the environment your customer controls. Fleetnook connects deployment, health and usage in one clear operating layer.
Start with your Temporal account. Keep the runtime close to your customer’s data.
DEPLOYMENT MAP CUSTOMER CONTROLLED
FLEETNOOKOperations
console
console
signed control +
allow-listed telemetryoutbound from customer environment
allow-listed telemetryoutbound from customer environment
YOUR CUSTOMER’S ENVIRONMENT
Agent runtimeDocker · customer network Ready
TemporalCloud or self-hostedBYO
Workflow data follows the customer’s configured services
One place to see the fleet.Customer keeps the keys.
01 Runs where your customer runs
02 Connects outbound
03 Measures what matters
04 Customer stays in control
01 / THE PLATFORMFrom handoff
to steady state
to steady state
Customer deployment should feel like a product, not a project.
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 pathOne approved image.
BOPERATIONS
See what’s running
across customers.
Track runtime health, resource use and reported token counts. Get a view of the fleet without collecting workflow payloads.
Explore the operations viewCCUSTOMER CONTROL
Customers stay
in the approval loop.
Customers approve deployments and can grant or revoke time-limited diagnostic access. Support sessions are not enabled yet.
See how control works02 / HOW IT WORKSFrom your build
From your build
to their boundary.
Fleetnook keeps the handoff simple and the operating picture connected.
View the runner guide- 01
Package the agent for deployment
Share an immutable image reference with your customer and distribute the signed Fleetnook runner bundle.
- 02
Customer enrolls their runtime
A small runner connects to Fleetnook over HTTPS from inside the customer environment.
- 03
Customer approves deployment
The customer reviews the requested image and resource limits before the runner starts it.
- 04
Operate with a shared view
Health and approved usage telemetry flow back. The agent runs locally; workflow history and model calls follow the customer-configured services.
03 / TRUST & CONTROLClear boundary.
Clear choices.
Clear choices.
Control belongs close to the customer.
Fleetnook connects the operating layer while the customer keeps their own runtime, Temporal endpoint and local credentials.
↑TELEMETRY
What Fleetnook receives
Allow-listed health, resource measurements and usage counters reported by the customer runner.
⌂CUSTOMER CHOICE
What stays local, and what you choose
Agent containers run in the customer environment. Workflow history is stored by the Temporal service the customer chooses.
✓EXPLICIT APPROVAL
What needs customer approval
Deployment requests and fixed diagnostic access. Interactive support access is planned and will require separate consent for each session.
TEMPORAL, YOUR WAY
Use the Temporal service you already trust.
Connect a self-hosted cluster or Temporal Cloud namespace. Managed Temporal hosting is on the roadmap.
04 / FOR DEVELOPERSKeep your agent.
Keep your agent.
Change the handoff.
Fleetnook works with containerized Temporal workers. Bring your image, your namespace and your customer’s deployment requirements.
Read the getting started guidecustomer environmentbash
# install the customer-side runner
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 run Outbound connection · ready for approval
05 / QUESTIONSBefore you
get started
get started
Good questions to ask.
Does Fleetnook host my agent?
The 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.
Can I bring my own Temporal account?
Yes. Connect Temporal Cloud or a self-hosted Temporal endpoint. Connection credentials are configured locally for the customer runtime.
Does workflow data pass through Fleetnook?
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.
Can Fleetnook support engineers open a remote shell?
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.
How does usage billing work?
Fleetnook can record customer-reported token and workflow counters, and show estimates using customer-approved rates. Independent reconciliation, invoicing and payment collection are not enabled.
FLEETNOOK · EARLY ACCESSBuild the agent.
Build the agent.
Make deployment repeatable.
See the operations console or start with the customer runner guide.