Enterprise readiness
Enterprise deployment options without fake procurement theater.
VeracityAPI defaults to privacy-safe logging and store_content=false. For teams that cannot send sensitive content to a shared API, the enterprise path is dedicated tenant, VPC/private networking, or self-hosted container evaluation. These options are not generally available yet; use this page as the current roadmap and procurement conversation starter.
Available now
store_content=falseby default for raw text non-retention.- Image endpoints avoid raw byte storage and log only hashed/domain metadata.
- Bearer API keys, prepaid usage, public subprocessors, and security posture pages.
Enterprise roadmap
- Dedicated tenant: isolated billing/logging and stricter retention controls.
- VPC / private networking: route traffic through private connectivity where the platform supports it.
- Self-hosted container: packaged worker/scoring path for regulated environments.
- Zero-data-retention contract: written retention guarantees and DPA-style terms.
Good fit / bad fit
| Use VeracityAPI enterprise when | Do not use it yet when |
|---|---|
| You need a content-risk gate for publishing, RAG/source triage, moderation, or training-data curation. | You need HIPAA/FINRA/legal-regulated processing under signed terms today. |
| You can start with metadata-only API mode while evaluating dedicated tenancy. | You require a self-hosted production container this week. |