Selected engagements across research computing, rural healthcare, regional telecom, and municipal cloud. The résumé behind the roster.
End-to-end delivery of a new HPC supercomputer for a federal satellite image processing contract — requirements analysis through go-live, plus two years of cluster support and management services.
UAF needed a supercomputer engineered for satellite image processing under a federal government contract — with demanding requirements on compute density, low-latency interconnect, and storage throughput, all delivered inside a strict program timeline and budget.
No in-house HPC architecture team existed at the scale this build required. The environment had to be designed, specified, built, tested, and documented by an external partner who could operate at the intersection of data-center design, networking, and HPC systems.
The HPC environment was delivered to UAF/RCS on the agreed timeline and within budget, passing acceptance testing and entering production for its federal contract workload.
Espira continued providing ongoing configuration assistance and cluster management services for two additional years, ensuring the research team could focus on science — not infrastructure ops.
Espira's team doesn't just execute — they design the thing you wish your in-house team had time to build. The HPC delivery came in on timeline and on budget.
Multi-year engagement designing and implementing disaster recovery, replacing storage, and rolling out modern device management for one of the largest rural healthcare corporations in North America.
YKHC operates across an immense rural geography delivering care to communities where downtime has direct patient-safety consequences. Their existing infrastructure lacked a proper DR posture for both virtual desktops and virtual servers, their storage fabric needed refresh, and their device estate was expanding faster than it could be centrally managed.
They needed a partner who could run three parallel programs — DR, storage refresh, mobile management — without the programs tripping over each other.
YKHC moved from ad-hoc DR planning to a tested, documented, executable DR posture across both VDI and virtual server estates. The storage fabric now supports its full healthcare workload with FAST-tiered performance.
The Workspace ONE rollout gave IT centralized lifecycle control over the device estate, simplified onboarding for new clinical staff, and hardened authentication with MFA/SSO to corporate SaaS.
Strategic cloud-migration plan connecting the city's existing data centers to AWS — aligning IT infrastructure with business objectives and carrying the entire stakeholder group through to a committed roadmap.
Municipal IT operates under a rare combination of constraints: public-sector procurement, fixed budgets, stakeholder committees, and workloads that can't afford missteps. Grand Junction wanted a cloud strategy — but one that didn't abandon their existing investments or create a rip-and-replace migration risk.
They needed an outside perspective that could translate enterprise hybrid-cloud thinking into a plan their department heads, city council, and IT operations team would all believe in.
A Strategic Plan for Cloud Migration the City could act on — with full stakeholder buy-in across IT, operations, and leadership. The hybrid model preserved prior investment in on-premises infrastructure while opening an AWS-based path for modernization and new workloads.
The education component meant the city's own teams didn't just adopt the plan — they could defend and iterate on it.
Dual-platform HA redesign of access and aggregation layers across three sites — protocol-driven failover, non-stop IP forwarding, and full knowledge transfer to CTC's field operations team.
CTC needed to evolve core IP services infrastructure to a dual-platform high-availability production operations model — with automation of network resiliency, protocol-driven fail-over, and non-stop forwarding. The stakes: maintaining IP service offerings for every customer through every migration event.
The engagement spanned the CTC central office in Cordova, an AT&T service POP in Valdez, and the AT&T Mobility head-end co-location in Anchorage — each with different operational teams, different coordination requirements, and zero tolerance for cutover downtime.
L2/L3 Cisco ASR 900-based platforms integrated and re-integrated across the three named sites. Greater overall data-bearer capacity, resiliency/redundancy strategies based on the binary-platform HA model, and dynamic L3 protocol-governed protection switching integrating both the undersea fiber segment (CDV-VDZ) and the terrestrial microwave backbone.
Every cutover completed inside its scheduled maintenance window. CTC's field operations team owns and operates the environment today.
Business continuity rebuild for a rural healthcare system — VEEAM deployment for on-premises and remote backup, paired with a staged hardware refresh that consolidated compute and storage into new rack infrastructure without interrupting clinical operations.
RMCH needed a credible disaster-recovery and business-continuity posture without the freedom to disrupt active clinical systems. The engagement had to deploy backup infrastructure, consolidate compute and storage into new racks, and relocate production equipment — all while the hospital continued to operate.
A working DR/BC solution with remote-site backup, plus a modernized and consolidated compute/storage footprint — all delivered around the hospital's clinical operating schedule.
Quick cards for a pair of engagements — details under NDA or omitted for brevity.
Data-center relocation assessment for the Archdiocese of Seattle, followed by an engagement to migrate and modernize applications and services into the public cloud.
Deployment of a new Horizon Virtual Desktop solution built on a 10-node VxRail cluster — HA firewalls, redundant core and management switching, backup, storage, and compute — through to production user migration.
If the above looks like the kind of work you'd want to commission, the fastest path is a 30-minute discovery call.
START A CONVERSATION →Tell us what you're trying to build. We'll tell you whether we're the right partner — or who else might be.