About
RocketPrint started as a fix for our own problem: our software knew exactly what should print, and had no dependable way to make it happen on a specific machine in a specific building.
What we believe
Three beliefs that show up in every decision we make about the product.
Most print integrations work on a good day. All the value is in what happens on a bad one — a computer asleep, your code retrying, a printer paused. That is where we spend our effort, and it is why queueing and safe retries are in every paid plan instead of held back for enterprise deals.
We publish what we cannot detect: completed means the print command succeeded, not that paper came out. Every compatibility claim says whether we have actually tested it. You should be able to rule us out from a web page in ten minutes rather than in week three of an integration.
Nothing connects in, no VPN, and no printer exposed to the internet. The app connects out and does one thing. Anything else would be asking an IT team to take a risk on our behalf.
How we work
You will not be passed through three levels of support to reach someone who can read the code.
A question about retries or job statuses reaches someone who wrote that code. Include a job ID and you will usually get a specific answer instead of a help-centre link.
Anything that changes how the product behaves goes on the changelog. Things we are still building are listed separately, so nothing reads as available when it is not.
Get in touch
Especially if it is a printer or format we have not tested — that is how the compatibility list gets better.