Proxylity UDP Gateway now supports credit card billing and introduces two named subscription plans: Professional and Enterprise. The pricing page has been updated with all the details, but this article walks through what changed, what didn't, and how to decide which option is right for you.
For customers already subscribed through AWS Marketplace on pay-as-you-go terms, nothing is different. The per-packet tiers are exactly the same. The per-Listener hourly charge is exactly the same. Your existing subscription continues without interruption or any action required on your part.
Pay-as-you-go remains available and is often the right starting point. There's no commitment, no monthly floor, and you pay only for what you actually use. At low to moderate traffic volumes it's hard to beat.
Usage-based pricing has two downsides that matter to certain customers.
The first is predictability. A per-packet model means your bill fluctuates with traffic. For teams with strict monthly budgets or finance teams that want a single line item, a flat subscription fee is easier to work with and plan around.
The second is risk tolerance. Applications may process bursty traffic — usually low, but occasionally very high. With pure usage-based pricing, an unexpected traffic spike translates directly to an unexpected invoice. For non-production workloads, those extra charges don't deliver value. And, even for production workloads, some teams prefer to have a hard cap on their costs rather than leaving them open-ended.
Neither concern invalidates usage-based pricing for the right workloads. But they're real considerations, and the new plan options are designed to address them.
AWS Marketplace is a genuinely excellent procurement channel. Purchases flow through your AWS bill, draw down AWS credits if you have them, integrate with consolidated billing, and simplify procurement for organizations with established AWS spending.
But it can add friction at the early stages. If you're evaluating Proxylity for a project and don't have permission in your organization to subscribe to third-party Marketplace products, you're blocked before you start. And some teams just want to put a credit card on file and move on — the procurement process for a quick proof of concept looks different from the right one for a production deployment.
Credit card billing is now available for the Professional plan and optionally for the Free plan (to release hard limits and allow overages). AWS Marketplace remains available and is still the recommended path for production workloads, enterprise procurement, and any case where you want usage to flow through your AWS bill.
The Free plan has always had two limits: 1 Listener and 1 million packets per month. With this update those become "hard" limits that can't be exceeded. When you reach either limit, the service stops processing additional traffic. It does not charge you. It does not quietly expand capacity and send you an invoice later. It stops, firmly, because free means free.
This matters for a specific reason: traffic spikes. If your UDP Gateway Listener receives an unexpected flood of traffic — whether from a bug, a misconfiguration, or someone testing your endpoint aggressively — the hard limit contains the exposure. You cannot accidentally spend beyond your Free plan.
No subscription is required for the Free plan. You can use it indefinitely without providing a credit card or creating an AWS Marketplace subscription.
If you're on the Free plan and want to lift the limits, you have two options: add a credit card, or subscribe via AWS Marketplace on pay-as-you-go terms. Both options allow you to release the hard limits or set different ones.
This is a feature that I think is easy to overlook but worth highlighting: hard limits are available to all customers as optional guardrails, not only on the Free plan.
If you're on a paid plan and want to cap your Listener count or packet volume to stay within a budget, you can configure those limits yourself. The service will enforce them the same way it does on the Free plan: by stopping rather than charging.
This is useful for limiting test environments, or for applications where you'd rather have a bounded outcome than an unbounded one. It puts the customer in control of the tradeoff between availability and cost.
Professional is designed for developers, small teams, and growing organizations that have outgrown the Free plan but aren't yet running the kind of sustained high-volume traffic that justifies Enterprise.
What's included:
The included allowances mean that for most moderate workloads — a handful of Listeners, traffic of several million packets per month — the bill is simply $49/month. Overages are charged at the standard per-packet tiers, the same as pay-as-you-go.
Professional was created for teams that want a predictable minimum cost and the flexibility to grow without committing to Enterprise pricing. It's the "I know what I'm building, I want it to be reliable, and I want a simple bill" option.
Enterprise is optimized for high-volume, continuous workloads for production environments.
What's included:
Batch pricing is the most significant structural difference between Enterprise and the other options, and it deserves an explanation.
When UDP Gateway delivers packets to a Destination, it collects them into batches — groups of packets sent together in a single API call. This is how delivery to SQS, Kinesis, Lambda, and other Destinations works efficiently at scale. With batch pricing, you're billed per batch delivered rather than per packet.
For low- and moderate-volume traffic, per-packet pricing is almost always cheaper. A batch containing a single packet costs $2.50/M batches, while per-packet pricing for the same packet is $1.25/M. If your batches average fewer than two packets, batch pricing is worse.
But for sustained, high-volume workloads, batches fill up. At a steady flow of several hundred packets per second, a typical batch size grows to dozens or hundreds of packets — all counted as a single batch in the billing model. The economics improve significantly compared to counting each packet individually.
As a rough crossover point: if your traffic consistently exceeds 400 packets per second, batch pricing is likely more cost-effective than per-packet pricing. Below that threshold, standard pay-as-you-go or Professional overage pricing will generally cost less.
Enterprise also removes per-Listener charges entirely. For organizations running many Listeners — dozens across a multi-tenant SaaS platform, for example — eliminating that per-Listener overhead can itself be a significant saving.
The enhanced SLA (99.99% vs. 99.9%) and priority support are there because at the workload sizes that justify Enterprise pricing, availability and response time genuinely matter more.
For customers with high and predictable packet volumes, pre-paid packet credits are available through AWS Marketplace contract offers. Pre-purchasing a year of credits at once can unlock per-unit pricing that's significantly lower than month-to-month rates.
As an example: a workload that handles a steady 100M packets per month pays $123.75/month on the standard per-packet tiers. Purchasing 1,200M packets (a full year) upfront costs $1,228.64 — a saving of $256.36, or about 17%.
If your volume is steady and you want to commit, it's worth looking at the contract offers in AWS Marketplace or contacting us to discuss options.
A few simple heuristics:
The full plan comparison, per-packet pricing tiers, and batch pricing details are on the pricing page.
Get started with Proxylity UDP Gateway today. No upfront costs — pay only for what you use.
Buy with AWS Try free with AWS View Pricing