Support
Something is not printing, a station will not connect, a job failed and the reason is not obvious. Send your organization name and a job ID.
Contact
Talk to the people who build it.
RocketPrint is small, which means an engineering question reaches an engineer. Include a job ID whenever you have one — it turns most questions into a two-minute answer.
Where to write
Four addresses, by what you need.
Security
Vulnerability reports and security questionnaires. We confirm receipt, keep you updated while we fix, and credit you if you want it. The model is documented on the security page.
Sales and volume
Volume rates, branded editions for platforms, or a procurement process that needs a human. You do not need to talk to anyone to start — see pricing.
Anything else
Feedback, a printer we should test against, or a use case you are not sure we cover.
Before you write
Three things that usually answer it faster.
Not deflection — this is the same checklist we would run.
Check the station is online
Console → Printers shows live presence. An offline station means jobs are queueing safely and will dispatch on reconnect.
Read the failure reason
A failed job carries the error the print system returned. It is usually specific enough to act on.
Check the docs
The error catalog covers every status the API returns and what to do about each.
Check status
If dispatch is broken for everyone, the status page explains how we communicate it.