Novus ecosystem documentation

Novus PDF Studio is the live PDF form-filling and signature editor in the Novus Stream Solutions portfolio. It runs at pdf.novusstreamsolutions.com. Its core workflow is the form editor: upload a PDF, scan likely fields with AI, refine every suggested layer manually, add missing text, number, checkmark/cross, date-style, or signature fields, draw a signature, and export or print the finished document. A blank-page authoring surface at /create starts from paper size, headings, images, tables, and shapes with selectable text. /sign-pdf is the dedicated signature workflow that says what a browser signature is and is not. /learn filters guides, tutorials, and workflows by the job you are doing. Alongside those, a suite of page tools is live at /tools — merge, split, organize, rotate, page numbers, protect (AES-256 passwords), unlock, compress, flatten, PDF-to-images, images-to-PDF, and OCR. This page reflects the product as it exists today. Redaction and metadata cleanup remain future possibilities, not current hub claims.

Novus Convert is the browser-first file conversion app in the Novus Stream Solutions portfolio. It converts and compresses files entirely on your device — with no account and no supported source files sent to a remote conversion service — and validates every result before a download is enabled. The workflow now spans 2,341 working routes over 274 documented formats, 244 of which are browser-ready inputs, across images (including camera RAW inputs), video, audio, documents, ebooks, archives, vector/CAD/3D meshes, and fonts — plus adjustable-quality compression for 125 same-format inputs, and mixed batches where each file can take a different output. The heavy lifting runs locally in WebAssembly — FFmpeg for audio and video, dedicated decoders for camera RAW formats, and pdf.js with pdf-lib for documents. Because the route matrix is so large, the live conversion directory at /conversions is the canonical, always-current list of every active input-to-output pair; 2,338 mature pairs and 243 format profiles are indexable, while newer fixture-pending routes stay noindex until their gates pass.