As a one person product team I was able to implement Apryse in a matter of days and offer a whole new set of features to our customers

Earlier on the documentation left me wanting more, but it has improved over the years.

I consider it as a leader in the industry.

Quite comprehensive product based on the company development with no dependencies -as far as I know- with open source libraries.

Moving from one version to another is not that smooth process. The product is rather expensive.

Sales team communicated that we could test the Webviewer module for free as it is open source, but having access to test the digital signature module we needed to subscribe the add-on. We were pressured in time and we agreed to pay in advance to have access to the feature. Wrongly were we aware that we could test the whole suite of add-ons for free using the trial key.After 6500$ invested in PDFTRON, their product simply didn’t work as advertised, leaving us empty handed and a whole mess to cleanup up in our product.I could stop here, but things got worse afterwards. We were extremely frustrated with this situation. Missing our go-live target was a strong blow to the team that had a major job to implement everything from scratch properly.So we reached out to PDFTRON to get our money back. We got barriers upon barriers, calls after calls, departments after departments and the same message “This issue is in management hands and I cannot do anything about it.”.Another module we requested was PDF/A conversion. After testing with many different files, we found one situation were the conversion failed. So we could not rely on it.For reference, we started implementation on September 12, 2022. Our go-live target was October 20, 2022. On November 30, 2022, we decided to give up on PDFTRON. On January 30, 2023 we are still waiting for a proper response and our money back.

Having a suite of products around PDF covers all our needs. Even though it didn’t work for us.

Our relationship was painful from the start.We were announced that our use case for digital signatures was pretty common and would be a 2 week integration effort.Those 2 weeks turned into more than a month!Working around PDFTRON Webviewer to customize behavior is almost impossible.We tried, unsuccessfully, manipulating the interface to implement a similar experience you get when signing in Docusign for example.If the UI is painful to work with, using the digital signature APIs a whole set of problems.Our requirement for digital signatures was to sign the document hash externally, through multiple providers, and use PDFTRON to complete the signing process.Well, after trying 3!! Different methods from their SDKs (Webviewer client side, Nodejs server side and Java server side) we always got different errors during API calls.We reported all this issues to their support and got into video calls with the product tech team as well. They got to see the errors first hand and could not reproduce. Please consider this fact as well: the time to answer a ticket was more than a week!! We had to pressure their team to get an answer and to this day no solution was presented. In the end we gave up.Pricing transparency is a big con in PDFTRON. Everything is an add-on, requiring specific licensing terms and contracts.

The pre-sales technical support was excellent and made it really fast and easy to spin up a POC .

PDFTron was by far the most feature rich product offering we looked at. Also the fact that they don't just wrap another open source rendering engine like PDFium gave us confidence they had built their product from the ground up and had total control.

The price tag was on the higher end compared to other alternatives but for enterprise software I think its worth it for all the features they offer. They were also flexible during pricing talks to find a comfortable landing spot that worked for both parties.

Great then frustrating. Great in that we were able to implement and tweak easily with your support team's help.Frustrating with certain "gotches" like client adding text to the DOCX file and seeing footers moved to next page. I have not been able to overcome that issue as yet.

Quick and easy implementation on a new project

I made use of a ready-made pdftodocx.exe from your downloads. It works well except for some things. I need to make use of the full SDK in order to take advantage of the latest developments as you are not providing a ready-made pdftodocx.exe any longer.