Is Proxylity ready for your
production workload?

Reliability you can check

Proxylity has maintained greater than 99.99% availability since launch. The architecture is designed so that nothing at the delivery or contols layers is a single point of failure: the gateway runs across multiple AWS regions with automatic failover, and for customers the serverless integrations mean there are no application servers to patch, restart, or lose quorum.

UDP Gateway is deployed as an AWS Marketplace product with AWS Qualified Software status — meaning AWS has reviewed it against their standards for production readiness. The listing also participates in AWS Marketplace Vendor Insights: enterprise security and procurement teams can request access to Proxylity's security profile — a structured set of controls with evidence continuously gathered from AWS Config and Audit Manager — instead of sending manual questionnaires.

The architecture is a deliberate hybrid: Proxylity operates the shared global infrastructure that terminates UDP and WireGuard connections and converts packets to JSON, while your data processing and storage stay entirely in your AWS account. Proxylity does not store the data passing through your listeners — packets are handed off and gone. Your Lambda functions, Kinesis streams, SQS queues, and other destinations receive the data directly, and you decide what happens to it from there.

This split keeps the undifferentiated infrastructure work off your plate while preserving your ownership and auditability of everything that matters. Data residency for compliance requirements is built in — you choose the AWS region your destinations run in, and delivery stays there. There's no extra charge for it.

Who's running it

Customers from individual developers to enterprise teams are running Proxylity in production across North America, South America, Europe, and Asia. The protocols in use span RADIUS, CoAP, DNS, syslog, NTP, IoT telemetry, and custom UDP applications. The architecture holds up under varied real-world conditions.

We don't publish customer or company names because we take the same approach to all customer data: we don't process or collect what we don't need. Subscribing on AWS Marketplace doesn't even require an email address. If you never want to hear from us, you never will. The best protection for sensitive information is not having it in the first place.

If you're evaluating UDP Gateway for a specific use case, or need guidance on integrating it into an existing architecture, we maintain a public examples repository with production-ready CloudFormation templates for common patterns. We also offer consulting engagements for teams that want hands-on assistance designing and launching implementations. Get in touch if that's useful.

Who built it

Proxylity was built by Lee Harding, a distributed systems engineer with more than 25 years of experience and a two-time CTO. The combination Proxylity requires — operating UDP infrastructure at scale and building reliable serverless pipelines — comes from having done both in production.

At Eleven Software, Lee ran a global Wi-Fi platform serving 9 million daily users, with RADIUS-over-UDP authentication processing 10,000+ transactions per second. That meant owning the servers, load balancers, patching cycles, and the 3am incidents that motivated building a better approach. At Zapproved, he built and operated an enterprise legal hold platform on Lambda, S3, SQS, and SNS for Fortune 500 clients, before serverless was a mainstream architectural choice. Before either, he spent more than a decade at Autodesk building performance-critical C++ systems.

The thinking behind Proxylity predates the company. SimplestLoadBalancer — an open-source stateless UDP load balancer — and Lee's writing on UDP and distributed systems both document the engineering thinking that led here.

LinkedIn | GitHub | Medium

Company

Contact

General inquiries: team@proxylity.com
Sales: sales@proxylity.com
Support: support@proxylity.com