Developer tools for .NET, built the way this kind of software should be.
A great deal of business software has quietly become someone else's service. The report your finance team prints, the document your customer signs — increasingly those are rendered on a machine you do not own, by a company you now depend on, and metered by the page.
We think a certain class of software has no business being a service at all. Generating a document from a template is a computation, not a relationship. It should run inside the application that needs it, on the same machine, with no account, no key rotation and no status page to check when it stops working.
That is the kind of software PorticoSoft makes.
Constraints we hold ourselves to, visible in the product.
Paragon ships as a NuGet package with no database and no service behind it. The consuming application keeps a folder of exported templates and calls one method. There is nothing to provision and nothing of ours in the request path.
Reports carry payroll, invoices and contracts. Every request a report makes outside its own folder is refused — its fonts, stylesheets and scripts travel inside it. That is enforced in code, which is why it can be tested, and it is.
A Paragon template is an HTML page with {{ }} bindings. Not a
designer format, not a binary, not something only our tooling can open. Your team
can diff it, review it and keep it in the same repository as everything else they
own.
Integrity hashes over templates and assets, provenance stamped into every generated document, and schema-version checks that stop rather than guess. A report that silently renders the wrong number is worse than one that refuses to render.
A portico is the part of a building you pass through on the way in — structural, permanent, and not the point of the visit. That is the right ambition for infrastructure software. It should hold weight and then get out of the way.
A licence is issued to your organisation rather than to a machine — install it on as many as you need. It runs to a stated expiry and covers a stated generation of the product, and the documents you have already generated stay yours whatever happens to the licence. Support and questions go to a person, not a queue.
If you are evaluating Paragon, the fastest way to start is to open a worked example and read the template it was generated from — then write to us about your own.
Install it free — the output is watermarked until you buy — and tell us what your hardest report looks like.
