Security & deployment
Keep print files where
your security policy requires.
Run in our hosted environment, on your own infrastructure, or on a network with no connection to the public internet. The same access controls and job history apply in each deployment model.
How Pluraprint secures a 3D printing operation
Uploaded design and sliced files are encrypted at rest, and connections among the web app, services, object storage, and site agents use TLS. Sensitive credentials, including printer access codes and SSO tokens, are encrypted separately before they are stored.
Access is controlled through roles and permissions, with SSO available for organisations that manage identity centrally. The audit trail records important changes, and air-gapped deployment is available when data cannot leave an isolated network.
Encryption
Files are encrypted in storage and in transit.
Pluraprint checks that object storage encryption is enabled before it will accept uploaded files. Data crossing service boundaries uses TLS, and file transfers use short-lived links instead of permanent public URLs.
Credentials need a different treatment from uploaded files, so printer access codes and identity-provider tokens are encrypted before they are written to the database. API keys are stored in a form that can't be reversed.
Encrypted file storage
Uploaded print files, thumbnails, and snapshots are stored with encryption enabled.
TLS in transit
Service and storage connections use TLS while data is moving.
Protected designs
Short-lived, single-purpose links are used for file transfers.
Managed keys
Self-hosted deployments keep application secrets and storage configuration in your environment.
Deployment
Run it entirely offline.
For the most sensitive environments, Pluraprint can be deployed self-hosted behind your firewall or fully air-gapped, with no dependency on the public internet.
In a self-hosted deployment, the database, object storage, application, and printer agents all run in infrastructure you control. Air-gapped installations use a manual update path.
Self-hosted
Deploy on your own servers or private cloud and choose when to upgrade.
Air-gapped
Operate on a network with no route to the public internet.
Firewalled
Keep the application and printer traffic inside your network perimeter.
Data ownership
Choose the database, object storage, backup policy, and retention period.
Governance
Control access and keep a record of changes.
Roles define what a person can do in the operator app and at stations. The audit log gives administrators a timestamped history to review when something changes.
Role-based access control
Build roles from individual permissions, then assign one or more roles to each user.
SSO & identity
Use your existing identity provider so account access follows your organisation's sign-in policy.
Tamper-evident audit trail
Configuration, permission, and approval changes are recorded with the person and time attached.
Our principles
Security choices you can inspect and configure.
Least privilege by default
Start with the permissions a role needs, and leave unrelated parts of the application out of view.
Your data is yours
Customer data isn't sold or used to train models. Self-hosting keeps it in infrastructure you operate.
Defense in depth
Storage encryption, TLS, access control, network boundaries, and audit logging cover different parts of the risk.
Transparency & accountability
Administrative changes and job decisions are attributed to the account that made them.
Questions
Security & deployment FAQ
What security and IT teams ask before approving a 3D printing platform.
Can Pluraprint run offline or air-gapped?
Yes. Pluraprint can run on your own infrastructure behind a firewall or on an air-gapped network with no dependency on the public internet. The application, database, object storage, and supporting services remain in the environment you operate.
How does Pluraprint protect uploaded design files?
Uploaded design and sliced files are stored with encryption at rest. Connections among the application, services, site agents, and object storage use TLS. Sensitive credentials are encrypted separately, and role-based permissions control what each account can do.
Does Pluraprint keep an audit trail?
Yes. Pluraprint keeps an audit log for important configuration, permission, and approval changes, with the account and time attached. Jobs also keep their own event history from submission through their final outcome.
Do you train on or share our data?
No. Customer data isn't sold or used to train models. A self-hosted or air-gapped deployment also keeps application data in infrastructure you operate.
Does Pluraprint support SSO?
Yes. Pluraprint can use an existing identity provider for sign-in. Roles and permissions still determine what each account can do inside the product.
Security reviews and deployment planning
Send us your hosting constraints or review questions. We'll walk through the deployment model, storage, identity, access controls, and update path.
Request a security briefinghello@pluraprint.com