reputation·pool
Get started
Reputation infrastructure for your resource pools

The reputation API for proxy & account pools.

Stop hand-rolling cooldowns, blocklists, and lease logic. Grab the healthiest resource and report what happened — a verified open-source engine keeps the pool healthy for you.

Get startedRead the docs

Powered by a fully open-source, formally-tested engine

Advisor.java
var lease = advisor.acquire("checkout-us");   // healthiest resource, right now
useResource(lease.resource());
 
// report the outcome — that's it
advisor.report(lease, Outcome.success(latency));
// on failure? report(lease, Outcome.failure(TIMEOUT))
// → the engine cools, isolates & re-probes automatically
Trust comes from the engine, not logos
Open sourcethe whole engine, on GitHub
Lincheckconcurrency proven correct
Mutation-testedtests that catch real bugs
Audit trailevery decision on record
Why teams switch

Bad resources step aside — you just use the healthy ones.

Automatic cooldown & recovery

Failing resources step aside, then earn their way back.

Just report what happened. When a resource keeps failing, the engine benches it for a cooldown and takes it out of rotation — then eases it back in over time to check whether it's healthy again. So a bad proxy fixes itself instead of ruining your run.

Per-context isolation

A problem in one place never spreads to another.

Reputation is tracked per resource × context — its own cell. If checkout-us goes bad on a proxy, search-eu on that same proxy is untouched — each context keeps its own health and cooldown.

Real-time dashboard

Watch every hand-out, cooldown, and recovery live.

Pool status, reputation curves, and a live event stream — at a glance, with no SQL and no guessing. Metrics also ship to /actuator/prometheus, straight into your own Grafana.

Everything included

Built for real automation infrastructure.

No add-ons, no paywalled basics — everything a serious workload needs is here from day one.

gRPC & REST

One engine, two ways in — gRPC for the fast path, REST for your tooling.

Live event stream

Subscribe to every hand-out, cooldown, block, and recovery the moment it happens.

Prometheus metrics

Scrape /actuator/prometheus straight into your own Grafana.

Audit trail

Every cooldown, block, and hand-out decision saved to a durable, queryable log.

Per-context reputation

Health tracked per resource × context — one context's failures never spill into another.

Open-source engine

The core is Apache-2.0 on GitHub. Self-host it, or let us run the hosted API.

How it works

Three calls. The engine does the rest.

Works over gRPC or REST — register your resources once, then grab one and report the result per context. Cooldown, isolation, and recovery are never your code to write.

  1. 1

    Issue a key

    Create an API key in the dashboard and point your client at the gRPC or REST endpoint.

    rp_live_…
  2. 2

    Register & acquire

    Register your resources once, then ask for the healthiest one per context.

    acquire("checkout-us")
  3. 3

    Report the outcome

    Tell the pool what happened. Cooldown, isolation, and recovery all happen automatically.

    report(lease, success)
Docs

Up and running in five minutes.

Issue a key, register a resource, then acquire and report — the quickstart walks the full round trip, in your language.

5 min

Quickstart

Key → Register → Acquire → Report, end to end, copy-paste ready.

Start building →Reference

API reference

Six gRPC RPCs and the REST control plane, every field documented.

Browse the API →Guide

Concepts

Reputation, cooldown, contexts, leases — how the engine actually thinks.

Learn the model →
Get access

We're onboarding teams one by one.

No self-serve signup yet — we set up each team by hand so your pool starts healthy. Tell us about your workload and we'll get you a key.

Email us

or write to [email protected]