Running as a Web Service
FormVu runs as a self-contained web service, accepting PDF Forms over HTTP and returning converted output through a REST API. There are four ways to deploy it depending on your infrastructure and operational preferences.
Deployment options
| Option | How it runs | Best suited for |
|---|---|---|
| Self-hosted: Java Application Server | Deploy to Tomcat, Payara, Jetty, GlassFish, or any compatible server on your own infrastructure | Teams with an existing Java Application Server estate |
| Self-hosted: Docker | Run the FormVu Docker image on your own servers or cloud VMs | Teams that prefer containerised deployments on their own infrastructure |
| Container platform | Run the FormVu Docker image on AWS ECS, Azure ACI, GCP Cloud Run, or Kubernetes | Cloud-native deployments requiring auto-scaling or managed container orchestration |
| FormVu Cloud API | Managed and hosted by IDRsolutions | Teams that want document conversion without managing any infrastructure |
Guides
Frequently asked questions
What Java Application Servers does FormVu support? FormVu can be deployed to Tomcat, Payara, Jetty, and GlassFish using the same package as the Docker deployment. Any Java Application Server that supports standard deployment is compatible.
Should I deploy FormVu using Docker or a Java Application Server? Both options run the same FormVu package as a self-hosted web service on your own servers or cloud VMs. Docker is the simpler path if your infrastructure already uses containers. A Java Application Server such as Tomcat or Payara is a better fit if you have an existing application server estate.