# Org-Wide Wildcard Certificates

**URL:** <https://community.fly.io/t/org-wide-wildcard-certificates/26132>\
**Category:** Questions / Help\
**Tags:** wishlist, certificates, login-only\
**Created:** [October 7, 2025, 11:43pm UTC](https://community.fly.io/t/org-wide-wildcard-certificates/26132 "2025-10-07T23:43:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ospade](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/ospade/32/37846_2.png) [@ospade](https://community.fly.io/u/ospade)\
**Post date:** [October 7, 2025, 11:43pm UTC](https://community.fly.io/t/org-wide-wildcard-certificates/26132/1 "2025-10-07T23:43:55Z")

</div>

Is this still in development? I have a similar use case and would like to create a custom subdomain per-customer app (fly-replay isn’t going to cut it). Ideally I wouldn’t have to create a central proxy with a wildcard cert, then flycast the user’s apps to the proxy’s network.

> [@Organization-scoped Wildcard Certificates](https://community.fly.io/t/organization-scoped-wildcard-certificates/19836/4):
>
> So first of all I want to congratulate you on your design, because this is exactly the type of design that we are building our platform for, so this question has prompted some good internal discussion. Maybe you know all this already, but this design exceeds the “Fly Launch” PaaS experience that we offer, and you’d be better suited to using the Fly Machines API directly, either through the CLI or through the HTTP API. If you haven’t read it yet, you should give a close read of [fly machine run](https://fly.io/docs/machines/flyctl/fly-machine-run/) a…

---

<div class="post-metadata">

**Author:** ![lillian](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/lillian/32/49616_2.png) [@lillian](https://community.fly.io/u/lillian)\
**Post date:** [October 8, 2025, 3:13am UTC](https://community.fly.io/t/org-wide-wildcard-certificates/26132/2 "2025-10-08T03:13:33Z")

</div>

I haven’t heard of that, I don’t think anyone is working on it at the moment.

these days, the best suggestion is to use a router app and fly-replay. this doc might not be exactly your use-case but it explains the flow: [Per-User Dev Environments with Fly Machines · Fly Docs](https://fly.io/docs/blueprints/per-user-dev-environments/)

---

<div class="post-metadata">

**Author:** ![bglw](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/bglw/32/51112_2.png) [@bglw](https://community.fly.io/u/bglw)\
**Post date:** [October 8, 2025, 8:40pm UTC](https://community.fly.io/t/org-wide-wildcard-certificates/26132/3 "2025-10-08T20:40:55Z")

</div>

Also of note, fly-replay has some new features since that post that help in these cases. Most importantly, there is now [Replay Caching](https://fly.io/docs/networking/dynamic-request-routing/#replay-caching). With cached replays you don’t have as much load on apps replaying, and you also alleviate most timing concerns since subsequent requests don’t need to first travel to your replaying app.

If fly-replay still doesn’t cut it, I’d love to hear why!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/fly1/original/3X/6/e/6e8955d00cb218e186ebbe3a6ab06fefdce15290.svg) [@system](https://community.fly.io/u/system)\
**Post date:** [October 15, 2025, 8:41pm UTC](https://community.fly.io/t/org-wide-wildcard-certificates/26132/4 "2025-10-15T20:41:45Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
