[GH-ISSUE #5467] Feature Request: Add auto-expiry / TTL support for Reverse Proxy Services #11256

Open
opened 2026-08-05 01:29:05 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @wgetnz on GitHub (Feb 26, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5467

Is your feature request related to a problem? Please describe.
I'm always frustrated when I create a Reverse Proxy Service for a temporary purpose — such as a demo, a short-term contractor access, or a development preview — and then forget to delete it afterward. There's no way to set an expiry on a service, so it stays active indefinitely unless I manually track and remove it. This creates unnecessary security exposure and operational overhead.

Describe the solution you'd like
I'd like the ability to set an optional auto-expiry (TTL) on a Reverse Proxy Service at creation or edit time. For example:

Expires after: 1 day / 3 days / 7 days / 30 days / Custom date

Once the expiry time is reached, the service should be automatically deleted (or at minimum disabled). The remaining time should be visible in the service list. Ideally, the Management API should also support an expires_at field (ISO 8601) so this can be scripted or automated via CI/CD pipelines.

Describe alternatives you've considered

Using netbird expose from the CLI, which already creates ephemeral services tied to the process lifetime — but this doesn't work for persistent, dashboard-managed services that need to last hours or days rather than just the duration of a terminal session.
Manually setting a calendar reminder to delete the service — this is error-prone and doesn't scale.

Additional context
This would be especially useful for use cases like: sharing QA environments with external reviewers, granting time-limited vendor access, or exposing webhook endpoints during a short integration window. A pre-expiry notification (e.g., 24h before deletion) would be a helpful addition as well.

Originally created by @wgetnz on GitHub (Feb 26, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5467 Is your feature request related to a problem? Please describe. I'm always frustrated when I create a Reverse Proxy Service for a temporary purpose — such as a demo, a short-term contractor access, or a development preview — and then forget to delete it afterward. There's no way to set an expiry on a service, so it stays active indefinitely unless I manually track and remove it. This creates unnecessary security exposure and operational overhead. Describe the solution you'd like I'd like the ability to set an optional auto-expiry (TTL) on a Reverse Proxy Service at creation or edit time. For example: Expires after: 1 day / 3 days / 7 days / 30 days / Custom date Once the expiry time is reached, the service should be automatically deleted (or at minimum disabled). The remaining time should be visible in the service list. Ideally, the Management API should also support an expires_at field (ISO 8601) so this can be scripted or automated via CI/CD pipelines. Describe alternatives you've considered Using netbird expose from the CLI, which already creates ephemeral services tied to the process lifetime — but this doesn't work for persistent, dashboard-managed services that need to last hours or days rather than just the duration of a terminal session. Manually setting a calendar reminder to delete the service — this is error-prone and doesn't scale. Additional context This would be especially useful for use cases like: sharing QA environments with external reviewers, granting time-limited vendor access, or exposing webhook endpoints during a short integration window. A pre-expiry notification (e.g., 24h before deletion) would be a helpful addition as well.
saavagebueno added the feature-request label 2026-08-05 01:29:05 -04:00
Sign in to join this conversation.
No Label feature-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#11256