Private beta · built for Temporal teams

Your agents.
Hosted your way.

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

AVAILABLE IN PRIVATE BETA

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 ↗
COMING LATER

Fleetnook-managed

Let Fleetnook provide and operate the environment. This hosting option is coming later.

See where everything runs.

The same approval path, with the Temporal service your customer chooses.

Illustrative example · not live status
Choose an example setup

Fleetnook console

Deployment requests
Customer decisions
Health & reported usage

Your operating view
Runner connects
outbound over HTTPS
No inbound port
for Fleetnook

Customer environment

Customer-controlled
Customer reviewThe customer approves the image and resource limits.

Fleetnook runner

Local credentials & signing key

Your agent

Approved image & resource limits

Customer-approved

Self-hosted Temporal

Workflow history in this environment

The customer supplies the host and Docker. Agent dependencies have their own network access.

  1. 01Deployment request
  2. 02Customer approval
  3. 03Runner ready
  4. 04Reported telemetry

Self-hosted Temporal can keep workflow history inside the customer environment. The agent runs on the customer’s host.

ONE CONNECTED OPERATING PICTURE

Your control plane.
Their place to run.

A deployment crosses the boundary only with customer approval. Health and usage bring the operating picture back.

Fleetnook control plane connected to an approved Docker runtime through illuminated paths for health and usage reporting.
Product illustration, not an application screenshot. Customers choose their own Temporal service, including Temporal Cloud or a self-hosted cluster.
01 / THE PLATFORMFrom handoff
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 path
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
BOPERATIONS

See what’s running
across customers.

Track runtime health, resource use and reported usage. Stale data stays visibly stale. Workflow payloads are outside the telemetry protocol.

Explore the operations view
CCUSTOMER 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 works
02 / HOW IT WORKS

From your build
to their boundary.

Fleetnook keeps the handoff simple and the operating picture connected.

View the runner guide
  1. 01

    Package the agent for deployment

    Share an immutable image reference with your customer and distribute the signed Fleetnook runner bundle.

  2. 02

    Customer enrolls their runtime

    A small runner connects to Fleetnook over HTTPS from inside the customer environment.

  3. 03

    Customer approves deployment

    The customer reviews the requested image and resource limits before the runner starts it.

  4. 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.

Control belongs close to the customer.

Fleetnook connects the operating layer while the customer keeps their own runtime, Temporal endpoint and local credentials.

↑

What Fleetnook receives

Allow-listed health, resource measurements and usage counters reported by the customer runner.

TELEMETRY
⌂

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.

CUSTOMER CHOICE
✓

What needs customer approval

Deployment requests and fixed diagnostic access. Interactive support access is planned and will require separate consent for each session.

EXPLICIT APPROVAL
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.

⌂Self-hosted◌Temporal CloudManaged · planned
04 / FOR DEVELOPERS

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 guide
customer environmentbash
# 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 run
05 / QUESTIONSBefore you
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?

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.

FLEETNOOK · EARLY ACCESS

Build the agent.
Make deployment repeatable.

See the operations console or start with the customer runner guide.

Fleetnook-managed hosting is coming

We haven’t implemented Fleetnook-managed infrastructure yet. You can bring your own AWS or Google Cloud environment, or connect an existing Linux host.

Your cloud account stays yours. Fleetnook brings deployments, approvals, health and usage into one console.

Bring your own cloud