Do you train on our data?
Never. Prompts, documents and audio are processed for your request only. Standard plans retain inputs for 30 days for abuse monitoring, and Enterprise plans can switch to zero retention — we also sign a DPA and, where needed, a HIPAA BAA.
Can we run the models on our own hardware?
Yes. Enterprise customers deploy the same serving stack into their own VPC or on-prem cluster — same API surface, same SDKs, your GPUs or your reserved capacity. We ship Helm charts, container images and a reference architecture, and our engineers run the first rollout with your team.
How accurate is the OCR, really?
On our public benchmark set of invoices, receipts and IDs, sapphire-ocr-v3 returns 99.2% character accuracy and 96.8% field-level accuracy. Every field comes back with a confidence score so you can route the uncertain 3% to a human review queue instead of guessing.
What stops someone cloning a voice they do not own?
Voice cloning requires a verified consent recording from the speaker, is limited to your organization, and every synthesis is watermarked in the audio signal. We take down reported misuse, and cloning is disabled by default on the Developer plan.
How does billing work when traffic is spiky?
You pay per million tokens, per page and per character of audio — no seat fees. Bursts are fine: we autoscale and bill the extra usage. To make invoices predictable you can reserve throughput, set per-key budgets and hard caps, and see spend alerts at 80% of any limit.
Is any of this open source?
The SDKs, CLI and our self-hostable gateway are MIT licensed, and we publish the serving benchmarks we use internally. If you would rather run everything yourself, start with the gateway and bring your own models — the API stays the same.