Platform features
The work around the printers, in one system.
Pluraprint handles the requests, decisions, queue changes, and records that single-printer tools leave to people and spreadsheets.
01 / Job Intake
Start with a sliced print file.
A requester uploads the output from their slicer. Pluraprint parses the file, detects the printer model and material requirements, then keeps the file and job details together through the rest of the process.
- →Sliced-file upload from the web or a station
- →Printer model and print details parsed from the file
- →Material requirements for each extruder
- →Project-tracking fields configured by administrators
- →Submission history for each requester
bracket_v3.3mf
Submitted by J. Kerr · 2 min ago
gear_assembly.3mf
Submitted by A. Reyes · 15 min ago
housing_final.3mf
Submitted by S. Tan · 1 hr ago
02 / Approvals & Moderation
Put the right checks in front of each job.
Rules can add approvals and other requirements to a job. Operators see what's still needed, review the parsed print details, and either prepare the job or reject it.
- →Approval requirements based on matching rules
- →Multi-stage approval when one sign-off isn't enough
- →Printer model and material review before queueing
- →Optional notes when rejecting a job
- →A timestamped record of each decision
Pending Review
J. Kerr
bracket_v3.3mf · 22 min est.
M. Lewis
fixture_a.3mf · 1 hr est.
C. Wong
enclosure.3mf · 2 hr est.
03 / Fleet & Queue Orchestration
Route work. Keep machines running.
Once a job meets its requirements, it joins the queue. Operators can manage priorities and printer availability, while requesters can follow the status of their own work.
- →Dispatch based on printer model and loaded material
- →Queue priority controlled by rules and operators
- →Live job and printer status
- →Printers can be marked down without losing queued work
- →Site-aware routing for distributed fleets
Print Queue · 4 jobs
S. Tan
housing_final.3mf
A. Reyes
gear_assembly.3mf
M. Lewis
fixture_a.3mf
C. Wong
enclosure.3mf
04 / Analytics & Reporting
Utilization, cost, and outcomes.
The analytics page turns print history into an operating view. Filter by site, printer, material, user, or time period, then inspect the jobs behind each result.
- →Job counts and completion time over a chosen period
- →Utilization by site and printer
- →Throughput and idle time
- →Success and failure rates
- →OEE for teams that use manufacturing metrics
This Month
247
Print Jobs
89
Active Users
91%
Success Rate
2.4 kg
Material Used
05 / Failure Handling & Notifications
A failed print stays connected to the job.
Mark the outcome, notify the requester, and create a reprint that keeps the original material requirements and settings. You don't have to reconstruct the job from an old message or file share.
Failure history
The failure is recorded against the job, printer, and its existing history.
Email notification
Email notifications can tell the requester that the job failed and needs attention.
Reprint from the original job
Create a new attempt from a failed, completed, or cancelled job without starting over.
06 / Security & Deployment
Choose where the system and its files live.
Use Pluraprint as a hosted service, run it on your own infrastructure, or deploy it on an air-gapped network. Uploaded files are encrypted at rest, and sensitive stored credentials are encrypted separately.
Encrypted storage
Pluraprint verifies that uploaded-file storage has encryption enabled before it will use it.
Offline & air-gapped
Run behind your firewall or on a network with no path to the public internet.
Access control & audit
Role-based permissions, SSO, API keys, and a timestamped audit log support controlled access.
FAQ
Feature questions
What is Pluraprint?
Pluraprint is software for running a shared 3D printing operation. It handles job submission, requirements and approvals, the print queue, printer management, pickup, and analytics. It sits above the slicer and vendor software rather than replacing them.
Who is Pluraprint for?
Pluraprint is for teams that run printers for other people, including university makerspaces, teaching labs, print farms, production teams, and research groups. It is most useful when submissions, printer decisions, and finished parts need a shared process.
How is Pluraprint different from a slicer or printer host?
A slicer creates the file a printer can execute, and printer software controls the machine. Pluraprint manages the job around that file: who submitted it, what requirements apply, where it sits in the queue, which printer received it, and how it ended.
Does Pluraprint replace our existing printers or firmware?
No. Pluraprint connects supported printers through on-site agents or vendor APIs and presents them in one fleet view. Your slicers, printer firmware, and vendor-specific machine controls remain part of the setup.
How long does it take to get started?
Setup starts with a site, an on-site agent where required, and at least one printer. After that, administrators configure users and roles, rules, quotas, notifications, stations, and optional modules as their workflow requires. The exact time depends on fleet size and deployment model.
How is Pluraprint priced?
Pluraprint is licensed per deployment. Pricing depends on the size of the operation and whether it is hosted, self-hosted, or air-gapped. Email hello@pluraprint.com with your fleet size and deployment requirements for a quote.
Feature deep dives
- 3D print queue softwareThe queue in depth: requirements, priority, printer eligibility, and dispatch.
- Printer fleet managementMachine state, model and material requirements, dispatch, and maintenance scheduling.
- Print farm softwareProduction workflows: order fields, job history, throughput, and cost inputs.
See the workflow with your own constraints in mind.
Tell us how jobs arrive today, who approves them, and what printers you run. We'll use that setup for the walkthrough.
Request a walkthroughhello@pluraprint.com