Click Below to Get the Code

Browse, clone, and build from real-world templates powered by Harper.
Repo
GitHub Logo

Harper Pro

Harper Pro builds on the open source Harper platform, adding replication, clustering, and certificate management to enable self-hosted distributed deployments. The source-available code supports production use while requiring compliance with licensing and restricting competing managed services.
TypeScript
Repo
TypeScript

Harper Pro

Harper
at Harper
April 13, 2026
Harper
at Harper
April 13, 2026
Harper
at Harper
April 13, 2026
April 13, 2026
Harper Pro builds on the open source Harper platform, adding replication, clustering, and certificate management to enable self-hosted distributed deployments. The source-available code supports production use while requiring compliance with licensing and restricting competing managed services.
Harper
Harper Pro builds on the open source Harper platform, adding replication, clustering, and certificate management to enable self-hosted distributed deployments. The source-available code supports production use while requiring compliance with licensing and restricting competing managed services.

Download

White arrow pointing right
Harper Pro builds on the open source Harper platform, adding replication, clustering, and certificate management to enable self-hosted distributed deployments. The source-available code supports production use while requiring compliance with licensing and restricting competing managed services.

Download

White arrow pointing right
Harper Pro builds on the open source Harper platform, adding replication, clustering, and certificate management to enable self-hosted distributed deployments. The source-available code supports production use while requiring compliance with licensing and restricting competing managed services.

Download

White arrow pointing right

Explore Recent Resources

Media Coverage
GitHub Logo

Harper Argues Against the Multi-System Stack and Releases 5.2

InfoQ examines benchmark results comparing co-located and serverless architectures, highlighting faster personalized-data paths, serverless advantages under heavy fan-out, and the performance implications of eliminating network hops between services at scale.
Media Coverage
InfoQ examines benchmark results comparing co-located and serverless architectures, highlighting faster personalized-data paths, serverless advantages under heavy fan-out, and the performance implications of eliminating network hops between services at scale.
Renato Losio, Staff Editor at InfoQ
Renato Losio
InfoQ Staff Editor
Media Coverage

Harper Argues Against the Multi-System Stack and Releases 5.2

InfoQ examines benchmark results comparing co-located and serverless architectures, highlighting faster personalized-data paths, serverless advantages under heavy fan-out, and the performance implications of eliminating network hops between services at scale.
Renato Losio
Aug 2026
Media Coverage

Harper Argues Against the Multi-System Stack and Releases 5.2

InfoQ examines benchmark results comparing co-located and serverless architectures, highlighting faster personalized-data paths, serverless advantages under heavy fan-out, and the performance implications of eliminating network hops between services at scale.
Renato Losio
Media Coverage

Harper Argues Against the Multi-System Stack and Releases 5.2

InfoQ examines benchmark results comparing co-located and serverless architectures, highlighting faster personalized-data paths, serverless advantages under heavy fan-out, and the performance implications of eliminating network hops between services at scale.
Renato Losio
Blog
GitHub Logo

Faster by Doing Less: How Harper 5.2 Engineers Database Performance

Harper 5.2 attacks database performance on three fronts: a per-worker record cache validated through lock-free atomic version slots, isolated commit scheduling to keep database writes off the application thread, and query planner improvements that route through the shortest available data path.
Cache
Blog
Harper 5.2 attacks database performance on three fronts: a per-worker record cache validated through lock-free atomic version slots, isolated commit scheduling to keep database writes off the application thread, and query planner improvements that route through the shortest available data path.
Person with very short blonde hair wearing a light gray button‑up shirt, standing with arms crossed and smiling outdoors with foliage behind.
Kris Zyp
SVP of Engineering
Blog

Faster by Doing Less: How Harper 5.2 Engineers Database Performance

Harper 5.2 attacks database performance on three fronts: a per-worker record cache validated through lock-free atomic version slots, isolated commit scheduling to keep database writes off the application thread, and query planner improvements that route through the shortest available data path.
Kris Zyp
Aug 2026
Blog

Faster by Doing Less: How Harper 5.2 Engineers Database Performance

Harper 5.2 attacks database performance on three fronts: a per-worker record cache validated through lock-free atomic version slots, isolated commit scheduling to keep database writes off the application thread, and query planner improvements that route through the shortest available data path.
Kris Zyp
Blog

Faster by Doing Less: How Harper 5.2 Engineers Database Performance

Harper 5.2 attacks database performance on three fronts: a per-worker record cache validated through lock-free atomic version slots, isolated commit scheduling to keep database writes off the application thread, and query planner improvements that route through the shortest available data path.
Kris Zyp