Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.velobase.io/llms.txt

Use this file to discover all available pages before exploring further.

A project is the top-level isolation unit in Velobase. Each project has its own API keys, customers, and billing accounts. Data never leaks between projects. Use separate projects to keep different apps, environments, or clients fully isolated. For example, you might create my-saas-prod for production traffic and my-saas-staging for testing — both live under the same organization, but their customers and balances are completely independent.

​
Creating a Project

When your organization has no projects yet, the dashboard shows an empty state with a prompt to create your first one. Click Create project, give it a name, and you are ready to go. Project names are for your own reference and can be changed later.

​
Project List

Once you have projects, the organization dashboard shows them as a card grid. Each card displays the project name, API key count, and customer count at a glance. Click any card to enter that project.

​
Inside a Project

After entering a project, a sidebar appears on the left with four sections:
SectionWhat it does
CustomersBrowse all customers, view individual balances, and inspect wallet categories.
LedgerFull transaction log — deposits, deductions, freezes, and unfreezes.
API KeysCreate, view, and revoke API keys scoped to this project.
SettingsRename the project or manage other project-level configurations.

​
Isolation Model

Each project is a fully independent billing namespace:
  • API Keys are scoped to a single project. A key from project A cannot access customers in project B.
  • Customers belong to exactly one project. The same customer_id in two different projects refers to two different customers with separate balances.
  • Billing records (deposits, deductions, freezes) are project-scoped and never cross boundaries.
This means you can safely use one project for production and another for testing without any risk of interference.

​
Tips

  • Testing: Create a dedicated project (e.g. my-app-test) instead of mixing test data into your production project.
  • Multi-tenant: If you operate multiple products, give each one its own project for clean separation.
  • Renaming: Project names can be changed at any time from the Settings page without affecting API keys or data.