Skip to main content

HARP is an API Runtime Proxy, a toolkit to enhance the speed, reliability and observability of external APIs.

Project description

HARP is an open-source API Proxy toolkit designed to improve the reliability, performance, security, and observability of the APIs you use. It runs in your infrastructure, close to your applications.

PyPI Artifact Hub GitLab CI/CD Pipeline Status Documentation Versions

Quick links: Documentation | Getting Started | Install (Docker) | Install (PIP) | Repository (Git) | CI/CD

Editions: HARP Community | HARP Pro | HARP Enterprise

Community: Subscribe to release announcements Join our discord server All Contributors

HARP is used both in development and production, and it works well for us. However, it is still under heavy active development and some features may not be as polished as you expect, and some APIs may change.

We are actively looking for feedback, please reach out with your thoughts, ideas, rants or issues. We can help.

What is HARP?

HARP is a python-based framework to build API proxies. From no-configuration 1 minute start to try it locally with an in memory database to a full production ready proxy with multiple storage backends and custom filtering, it got you covered.

The main goal is to improve the performance, reliability, security, and observability of the APIs you already use, without changing anything except the base URL of your API calls. Ultimately, you can use HARP to “fix the Internet,” or at least the subset your application depends on.

Out of the box, you’ll get standard-compliant caching (based on hishel), a world class http client (based on httpx), a circuit breaker, a python-based rules engine, an audit log and an observation dashboard. The features guide will tell you more.

HARP Proxy Overview

To instantly get insights on how your application is interacting with external services, you get a full searchable transactions audit trail, with detailed information on each request and response.

HARP Proxy Transactions

No more doubts about what happened. Now, you *know*.

Discover all HARP Proxy features

Getting Started

The quickest way to try HARP is using uvx:

# Run HARP directly with uvx
uvx harp-proxy --help

# Start a proxy with example configuration
uvx harp-proxy server --example sqlite --example proxy:httpbin

For more installation options:

  • Quick & Easy: Use uvx (shown above) - runs without installing HARP globally

  • Traditional Python: pip install harp-proxy - for standard Python environments

  • Containerized: Docker - for production deployments

  • From Source: Development setup - for contributing

Refer to the Getting Started Guide for detailed instructions.

How it works?

Overview

An overview of how HARP works in your system
  • Easy Integration: Integrating with your application is a breeze, because it speaks the same language you already use: HTTP. Simply run the proxy, update your API endpoints, and you’re ready to go. No complex setup or extensive configuration required. Of course, everything is modular and configurable, so you’ll be able to fine-tune for your taste later.

  • Reduced Network Distance: As a nearline proxy, HARP minimizes the network distance between your application and external services, when possible, using standard techniques like caching or prefetching. This leads to faster response times and improved overall performance of your application, even before any configuration is done.

  • Simplified Development: HARP eliminates the need for writing extensive code for functionalities such as caching, monitoring, alerting, rate limiting, circuit breaking, retries, tracing, logging, and more. These features can be easily delegated to the proxy, reducing the amount of code you need to write and maintain.

  • Seamless HTTP Integration: HARP seamlessly integrates with your application using the HTTP protocol. This means that the integration or removal cost is virtually zero, or even negative when considering the reduction in code you won’t need to write.

Read the full documentation

Hub to external services

An overview of how HARP works in your system when you have multiple consumers
  • Mutualize Client Logic: Having n API consumers does not mean you have to implement n times each client-side feature. Use HARP as a hub and greatly reduce the amount of client code you need to write and maintain.

  • Observes and Controls: You get a central place to observe and control all your API interactions.

  • Grow and Scale: As your company grows and develop new applications, you can leverage the work done on existing external services without having to write a single new line of code.

Service

Within the service, harp runs one or more proxies, each one listening to one port to instrument your external API calls with the features you need (auditing, caching, alerting, circuit breaker switch, health checks, etc.).

Each proxy is configured to intercept and forward requests to a specific external API, with independent configuration.

An additional (optional) port serves a dashboard to observe your proxies in real-time.

What happens within the harp service
  • Features: Harp comes builtin with a set of industry-standard client side features that you can leverage with a few lines of configuration.

  • Flexibility: Each feature is optional, and it’s up to you to chose the setup that fits your needs.

  • Customizable: You can write code to extend the proxy features, using the same interface as all the builtin features. It guarantees that you can basically implement pretty much anything that make sense inbetween your applications and the external services.

Proxy

As an HTTP Proxy, HARP does not change anything to the way you communicate with the external services. You were speaking HTTP before, you will still speak HTTP. The only change needed in your applications configuration to plug or unplug HARP is the base endpoint of the external services. In a modern 12factor-like application, it usually only means changing an environment variable.

What happens within one harp proxy
  • Reversibility: By requiring 0 code change on your application side (except endpoint url configuration, that should be outside the code if you follow the 12factor principles), HARP can be plugged and unplugged at a very low cost. You have absolutely no vendor lock-in.

  • Sidecar: Harp runs in your infrastructure, implementing the client side features right next to your application. The service is fast, and the minimum network distance between your application and the proxy makes it even faster.

  • Open Core: Harp is an open software. The core and reference implementation of the proxy is open source, and you can extend it to fit your needs.

Proxy features

Here is a non-exhaustive list of HARP Proxy’s main features:

You can read more about all HARP Proxy features in the Features Guide.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

harp_proxy-0.9.1.tar.gz (687.9 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

harp_proxy-0.9.1-py3-none-any.whl (831.8 kB view details)

Uploaded Python 3

File details

Details for the file harp_proxy-0.9.1.tar.gz.

File metadata

  • Download URL: harp_proxy-0.9.1.tar.gz
  • Upload date:
  • Size: 687.9 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.7

File hashes

Hashes for harp_proxy-0.9.1.tar.gz
Algorithm Hash digest
SHA256 2f39d83e0bd72de13f1ed24d64c602aae1384460049f2c313415c41a2bd82c69
MD5 89ad6829cda1f39cc2579231a33bd4d1
BLAKE2b-256 90b70d38e02500a27919fc79fe467dbd64b0e45a6a060139ba0f64e0558e946b

See more details on using hashes here.

Provenance

The following attestation bundles were made for harp_proxy-0.9.1.tar.gz:

Publisher: cicd.yml on msqd/harp

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file harp_proxy-0.9.1-py3-none-any.whl.

File metadata

  • Download URL: harp_proxy-0.9.1-py3-none-any.whl
  • Upload date:
  • Size: 831.8 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.7

File hashes

Hashes for harp_proxy-0.9.1-py3-none-any.whl
Algorithm Hash digest
SHA256 83c70db6723cf2765ea5dba10b1b48ef56b17325a1dcc164481dde52fb8a9400
MD5 b33e23f398cfe4292e9d73fdcea0f5ac
BLAKE2b-256 51742163a1c46dad7a2fbe026ddb8f2b805bdbbc145b1730a63fef8b170db116

See more details on using hashes here.

Provenance

The following attestation bundles were made for harp_proxy-0.9.1-py3-none-any.whl:

Publisher: cicd.yml on msqd/harp

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page