Technical brief
Local-first deployment overview
See how workflows stay close to local data, approved models, and lab software.
Read workflow guideResources
Connect software. Automate workflows. Track scientific work.
Read clear guides for technical teams, quality teams, lab IT, facility operators, and workflow owners.
Quality evaluation
Compliance workflow guide
Check how actions, file details, checksums, reviews, and approvals stay ready for inspection.
Read workflow guideProduct guide
Workflow automation patterns
Turn steps, files, settings, checks, notes, and results into a repeatable workflow.
Read workflow guideEvaluation guide
Software integration guide
Review which tools can connect, what outcomes they support, and where people approve the work.
Read workflow guideDeployment guide
Security and deployment brief
Compare workstation, lab, local server, and air-gapped setup options.
Read workflow guideBuyer checklist
Data integrity evaluation checklist
Check how users, files, versions, scripts, changes, and reviews stay linked to each run.
Read workflow guideGet clear answers to common questions.
What can my team automate?+
Connect and automate scientific software. Scientists can describe work in their own words, review the steps, run the workflow, and track every action, file, setting, and result.
Is PixeSci a cloud workflow platform?+
No. Workflows run locally by default, close to the software and files your team already controls. Teams can also connect approved internal systems and run workflows on their own servers.
Can PixeSci be deployed on-premises or air-gapped?+
Yes. Teams can run workflows on their own servers or in an air-gapped environment. Workflows do not need a cloud service to run.
Can PixeSci use AI without sending data to the cloud?+
Yes. Teams can use approved AI models that run locally or inside their own infrastructure. Available features depend on the models and setup your team approves.
Does PixeSci replace LIMS, ELN, CDS, or QMS platforms?+
No. Keep those systems as your official records while workflows move approved work between them.
How does PixeSci integrate with existing scientific software?+
Start with the tools, file types, review points, and outcomes your team needs. Each tool and version must be tested in the environment where it will run.
Is PixeSci built for regulated scientific workflows?+
Yes. Teams can track workflows, records, changes, reviews, and data integrity. Customers still must validate the system, maintain SOPs, train users, and meet their own regulatory duties.
How are audit trails and workflow history handled?+
Workflow steps, file movement, user actions, system events, and results can stay with each run. Your setup and policies determine how long records are kept and how teams review them.
How does PixeSci help teams repeat and track work?+
Keep steps, files, settings, users, and results linked to each run. Teams can use this history to review, repeat, investigate, and standardize their work.
What about validation and change control?+
Track workflow versions, settings, changes, and run history. Each organization must decide how to validate and control those changes.
Does PixeSci guarantee regulatory compliance?+
No. Software alone cannot guarantee compliance. Teams can run controlled workflows and produce records, audit trails, file history, user links, and review history. Compliance still depends on how the customer validates, configures, and operates the system.
Are all named software integrations production-ready?+
No. The catalog shows target software and possible ways to connect it. Teams must confirm readiness for each tool, version, setup, and use case.
Plan each setup around your software, workflow, environment, and review needs.
Test each software connection and complete the validation your environment requires.
Workflow mapping
Review one workflow from start to finish.
Bring your software, setup rules, data flow, and record needs.