Open weight and self-hosted

Replicate cost tracking

Per-second compute across public and private models.

How does Camaze work with Replicate?

Camaze connects to Replicate with read-only credentials and pulls spend and usage into the same view as every other place you pay for AI.

What gets collected

What Camaze pulls from Replicate

Camaze connects to Replicate with read-only credentials and pulls spend and usage into the same view as every other place you pay for AI.

  • Compute spend, split out of the wider cloud or platform bill
  • Which models and endpoints that compute is serving
  • Utilization, so an idle dedicated endpoint is visible as an opportunity
  • Cost per million tokens served, comparable to hosted providers

See your Replicate spend in context.

Book a walkthrough and we will show you Replicate costs next to everything else you pay for AI.

FAQ

Questions people ask

What access does Camaze need for Replicate?

Read-only billing and usage credentials. Nothing that can spend money, change a deployment, or read your prompts and completions. Details are on the security page.

Does it backfill historical Replicate spend?

Yes. Camaze pulls the available history on connection, typically the last twelve months, so you start with a trend rather than an empty chart.

Can we split Replicate spend by team or project?

Yes. Map keys, projects, workspaces or tags to your own org structure once, and every Replicate charge is attributed from then on. See cost allocation.

Do we have to use Replicate exclusively?

No. Camaze is built for the opposite case. Replicate sits alongside every other provider, tool and self-hosted model in the same view, on the same cost basis. It is equally useful if Replicate is the only thing you run: see single-provider visibility.

See where your AI money is going.

A 30 minute walkthrough of Camaze on your own numbers. You will leave knowing what you spend and where the savings are.

5 minute setup. Read-only. No engineering time needed.