Every team building on scientific software hits the same wall eventually. PESO exists to move that wall.
Without a shared ecosystem
- Installing third-party libraries breaks on dependency mismatches
- Version updates introduce breaking changes downstream
- Portability across CPUs, GPUs, and new architectures is manually managed
- Build times balloon as projects and dependencies grow
- New tools disrupt existing team workflows
- Libraries fall out of date, hurting performance and security
With PESO
- A curated, tested library portfolio via Spack + E4S
- Coordinated release and compatibility testing across the ecosystem
- Ecosystem-wide CI testing across CPUs, GPUs, and emerging architectures
- Shared Spack build caches cut compile times across teams
- User- and developer-experience research built into every release
- Ongoing software quality assurance and supply-chain security
Want the rest of the story? See PESO Project Details for how PESO operates, its guiding principles, and key activities.