Bosca / Gateway

Bosca Gateway

Your services,
behind one front door.

The Gateway is a managed reverse proxy: put any HTTP service you run behind a Bosca-authenticated path. Your sign-in, your groups, and your rules decide who gets through.

How it works

Register, bind, route.

01

Register the upstream

Point a gateway at the service's URL, give it a health probe, and tune its timeouts and connection pool.

02

Bind a route

Match a path pattern — and optionally a host — to that upstream. Pick the sign-in method and the groups allowed to read and to write.

03

Traffic flows

The proxy authenticates each request, injects the caller's identity as headers if you want it to, and forwards — reporting the upstream's health back to Studio.

What makes it powerful

A real proxy. And part of the platform.

The routing, health checks, and tuning you expect from a reverse proxy — with the platform's own accounts, groups, and tokens deciding who gets through.

Any HTTP service

Dashboards, query engines, internal tools, that one legacy box — if it speaks HTTP, it can sit behind the gateway.

Bosca sign-in in front

Per route: tokens for automation, the Studio session for people, username-and-password for older tools, or public — the same accounts as the rest of the platform.

Groups decide access

Reading and writing are granted separately, each to the groups you choose. API tokens also need the matching gateway scope.

Health, watched

The proxy probes each upstream on your interval and reports up, down, or unknown — with the failure reason — right in Studio.

Precise matching

Prefix, single-segment, and exact path patterns; literal and wildcard hosts with clear precedence; a sort order for ties.

Identity, forwarded

Inject headers on the way through — including the caller's email, subject, and groups — so the upstream knows who's asking.

Tuned per upstream

Connect and request timeouts, pool size, and idle limits are set on each gateway, not globally.

Presets for the fiddly ones

A preset fills in the fields a service is picky about — the data-warehouse preset sets the path and prefix handling, and flags what the warehouse itself needs configured.

Deep platform integration

Not a silo — part of the whole

The gateway doesn't bring its own user database or its own admin tool. It borrows the platform's — and that's the point.

  • Sign-in is Bosca's sign-in — the same accounts, browser sessions, and API tokens as everything else. No separate credentials to manage.
  • Access rules are Bosca groups — the group that runs your analytics is the group that reaches the warehouse behind the gateway.
  • Everything is managed in Studio — upstreams, routes, and live health on one screen. The proxy picks up changes on its own; there's no restart and no config file to ship.
  • Upstreams learn who's calling — injected headers carry the signed-in user's identity into services that have no idea what Bosca is.
connected
Access via the analysts group
API token · scope gateway:read
Identity headers → upstream
Upstream health, live in Studio

Gateway ships with Bosca

Every platform accumulates internal services that deserve better than a bare port. Put them behind the front door you already have.