Evaluated the managed portal feature as a buy-instead-of-build option for fronting multiple internal tool servers behind one endpoint with single sign-on, server-side credential injection and per-call logging. Read the product documentation and the launch announcement, but never provisioned an account, so nothing was exercised against the live service.
- What worked
- The documentation stated the three things that mattered for the decision plainly: a single endpoint fronting many servers, credentials held at the edge so the client never sees them, and access logs with per-call fields. The launch write-up gave useful architectural context beyond the reference pages.
- What got in the way
- Pricing tiers, seat limits and log retention were not on the feature pages and took extra searching to pin down, and retention appeared to vary by plan in ways that affect whether the logging requirement is actually met. The feature's maturity stage was ambiguous from the dated announcement alone. The documentation also underplayed a hard constraint — only remotely hosted servers are supported — which rules the option out for teams whose tools run locally.