DEV Community

yutianle
yutianle

Posted on

Tsuru at 130 title matches: a platform API with team-scoped deployment authority

Tsuru at 130 title matches: a platform API with team-scoped deployment authority

Tsuru is a PaaS that lets teams deploy and manage applications through an API. The API server holds application definitions, teams, roles, permissions, service instances, events, and the router configuration that places applications on the network. A public Tsuru endpoint is a deployment control plane.

On November 18, 2026, ZoomEye returned 130 matches for title="Tsuru" and zero for app="Tsuru" with sub_type=all, page 1, and page size 1. The title may match documentation or content about the platform rather than a running API. The count is not a list of exposed Tsuru installations.

Tsuru's documentation describes native authentication, OAuth, tokens associated with a team, roles, permissions, and event visibility. Its configuration reference includes HTTP server and authentication settings. The API is used to create applications, deploy units, manage service instances, and inspect events. Those operations are only safe when the identity is mapped to the correct team and the role prevents cross-team changes.

Authorization follows the team

A platform administrator can manage the whole Tsuru installation. A team owner can manage the team's applications and members. A developer may deploy code but should not be able to change the router, inspect another team's logs, or create a service instance with broader credentials. The API should enforce these distinctions even when the request comes from a CLI rather than the web interface.

Inventory tokens by team and owner. A token created for one team should not authenticate as another. Revoke tokens that were copied into CI output, shell history, or a repository. If native authentication is enabled, check the registration policy and password reset path. If OAuth is used, verify the issuer, audience, and scope mapping to Tsuru roles.

Application deployment can itself change the security posture. A user who can set environment variables may place a database password in an application. A user who can choose the router may redirect traffic or bind a new hostname. Review which roles can access those operations and whether the platform can restrict them per environment.

What to inspect on an owned instance

Check whether the API is reachable without a token, whether the login or registration page exposes the tsuruTarget, and whether administrative endpoints return distinct errors. Verify that a low-privilege token cannot list another team's apps, events, or service instances. Review the router API separately from the Tsuru API. A router that trusts requests from the platform may be reachable on a different interface.

Map the service layer. A Tsuru service instance may contain a database or object-store credential that applications use. If an application can create a service instance for an admin-only plan, the platform's role model has a gap. Review quotas, plan access, and the credentials passed to applications. Use short-lived or scoped service credentials where the broker supports them.

The scan count should be used as a prompt for ownership review. Search the internal inventory for Tsuru API hostnames, router endpoints, and control-plane ports. Compare those records with the public DNS and certificate inventory. For a match that belongs to the organization, document the authentication mode and the team/role mapping before testing any application action.

Why the title count is not the exposure count

"Tsuru" is a short product name and can appear in other contexts. A title match may be a blog post, documentation, a demo, or a reverse-proxy error page. The zero application count tells us that the simple app="Tsuru" label did not classify a matching page; it does not tell us whether a Tsuru API is accessible under another title.

The safer conclusion is architectural. Tsuru's API is powerful by design because it deploys and manages applications. It needs a strong identity provider, a clear team boundary, an auditable token lifecycle, and network isolation from the public internet unless the organization deliberately runs a public PaaS. A public title count is only a first hint.

Query evidence

title="Tsuru"
sub_type=all, page=1, pagesize=1, observed 2026-11-18T07:41:36+08:00, count=130
Enter fullscreen mode Exit fullscreen mode

References

Top comments (0)