Simple usage-based plans.

The private alpha converts DOCX and HTML to PDF. XLSX, PPTX, public URLs and common image formats (PNG, JPEG, TIFF) are planned, with PDF/A as an additional output. The final list will depend on what beta users actually need, so tell us about your formats when you sign up.

Only for as long as a job needs them. In the private alpha, originals and results are kept in private object storage for 24 hours and then deleted automatically. Files flagged by the malware scan are deleted immediately. You can also delete a document and its derivatives on demand with DELETE /v1/documents/{id}.

Yes, that is part of the plan. The platform is being built so that the API and its processing workers can run inside a customer VPC, on Kubernetes or on OpenShift. It is on the roadmap, not available during the first beta.

Yes. Signing PDFs (PAdES) and validating existing signatures are planned right after the core conversion features. Customers will be able to use their own certificates.

The REST API is the product. It is versioned, described with OpenAPI generated from the code, authenticated with API keys, and built around asynchronous jobs, idempotent requests and structured errors. Today it serves invited teams in a private alpha. SDKs for Java, JavaScript / TypeScript and Python will follow.

We do not have a public date yet. We will invite people from the waitlist in small groups, starting with teams whose use cases match the first features. Joining the list is the way to get in early.

Every file is scanned for malware before a conversion engine opens it, engines run in isolated containers with no internet access, API keys are stored hashed, requests are rate limited per key and every step is recorded in an audit trail. Files travel over TLS in production and are deleted according to the retention policy. We do not hold certifications such as SOC 2 or ISO 27001 today and will say so plainly until that changes.