Plurence is currently in Public Beta. Features and pricing may change. Not recommended for production workloads. Beta Terms

Core Concepts

Projects & API Keys

Projects are the primary isolation boundary in Plurence. Each project has its own API keys, usage quota, and audit trail.

What is a project?

A project represents one logical workload — a product, a service, a team, or an environment. Common patterns:

  • One project per environment: production, staging, development
  • One project per product or microservice
  • One project per team or cost center

Each project is isolated — API keys from one project cannot access another project's quota or see its audit log.

API keys

API keys are scoped to a project. A project can have multiple keys (useful for rotation or per-service isolation). Each key authenticates gateway requests and attributes usage to the project.

Key properties

Name Human-readable label (e.g. "production-backend")
Created at Timestamp of key creation
Expires at Optional expiry date. If set, key stops working after this timestamp
warning

API key values are shown only once at creation time. If you lose a key, delete it and create a new one.

Creating a project

  1. Go to Projects in the dashboard.
  2. Click New Project.
  3. Enter a name and optional slug. The slug is used in the API and cannot be changed later.
  4. Click Create.

Your first project is created automatically when you sign up.

Usage isolation

Quota and rate limits are enforced per project. Usage data — token counts, request counts, latency — is broken down by project in the Usage panel. The Audit log can be filtered to a single project.

Related