Getting started
What is Kivora and who is it for?
Kivora is a billing platform for AI products. Teams use it to support subscription, usage, and outcome‑based pricing with minimal engineering work.
How do I integrate Kivora?
Add the client SDK to capture events and use our server libraries or REST API to create customers, plans, and invoices. Most customers start by tracking 1–2 core events, then expand from there.
Do you offer a free plan?
Yes. You can start for free and upgrade as you grow. The free tier includes generous event and customer limits for evaluation and small projects.
Can I migrate from existing billing tools?
We provide import tools and guidance to move from Stripe Billing or spreadsheets. Our team can assist with mapping products, prices, and historical usage.
Pricing & billing
Which pricing models are supported?
Subscriptions (monthly/annual), usage‑based (per token, request, GB, etc.), one‑time charges, and outcome‑based models that bill on verified results.
How does usage‑based billing work?
You send usage events to Kivora. We aggregate them in real time, apply your pricing rules, and generate line items and invoices automatically.
Do you support taxes and invoices?
Yes. Kivora generates tax‑aware invoices and supports exporting invoice data to your accounting tools.
What payment providers can I use?
Kivora works alongside payment processors. Stripe is commonly used; others can be connected via webhooks and custom flows.
Technical & integrations
Which languages and SDKs are available?
JavaScript/TypeScript, Node, and Python SDKs are available, with a REST API for any stack. Webhooks support server‑to‑server workflows.
Can I export my data?
Yes. Export customers, events, and invoices at any time via API or CSV. Your data is always yours.
How real‑time is the usage tracking?
Events are processed as they arrive and reflected in dashboards within seconds, enabling accurate, up‑to‑date billing.
Do you have webhooks?
Yes. Subscribe to events like invoice.created, usage.updated, and customer.portal.accessed to automate workflows.
Privacy & compliance
Where is my data stored?
Data is stored in region with geo‑replication for durability. Access is restricted with role‑based controls and audit logging.
Do you support GDPR/CCPA?
Yes. Data subject requests, consent controls, and configurable retention policies are supported. We provide a DPA upon request.
Is data encrypted?
Yes. Data is encrypted in transit (TLS) and at rest. Secrets are stored securely with rotation policies.
Can I choose the region for storage?
Yes. Choose preferred data residency during onboarding and update it per‑workspace as needed.