Reach the software you install at customer sites

Give your support team access to a specific application inside an authorized customer network. A publisher at the site connects outward to Tubu.

Connect a customer’s status API

On an authorized machine at the customer site, replace the target with the address of an API that already requires authentication. Use your own Tubu hostname.

Set TUBU_TOKEN to your Tubu API key in this shell.

npx tubu-cli http http://192.168.1.20:8080 \
  --domain site-api.tubu.dev

Keep the publisher running. From your support machine, call the same status path at https://site-api.tubu.dev using the application’s credentials.

Choose one pilot site

Identify the service your support team needs, who authorizes access, and which machine can reach it.

Test a real support task

Protect the published HTTP endpoint with a shared secret or application authentication. Run one diagnostic request and verify the response with the customer.

Scope a custom plan

Tell us the number of sites, simultaneous connections, expected traffic, and support requirements. We will use those details to discuss pilot scope and pricing.

Discuss your first site

Describe the application, your site count, and the support task you want to test.