Compare
Kong is a gateway company adding billing. Farther Shore is a business platform born with the gateway, billing, and portal as one compiled artifact.
Direction. Kong starts from the industry's most battle-tested gateway and is adding metering and billing on top — OpenMeter acquired September 2025, Metering & Billing GA December 2025, prepaid credits July 2026. Farther Shore starts from the business: one TypeScript file compiles into the gateway, meters, Stripe-settled billing, portal, and docs together.
Sources: Kong press room · openmeter.io
No — you bring your own Stripe. Kong's setup guide instructs you to 'copy and save your Stripe API key from your dashboard'; Kong handles the catalog, rating, and invoice generation, while Stripe stores cards and collects the money. Farther Shore also settles through Stripe — but sells the whole flow, signup to checkout to keys, as one portal.
Sources: Kong Stripe integration guide
Kong's Dev Portal is real — branded, self-serve app registration, OpenAPI docs, custom CSS — but checkout is a generated Stripe Checkout link, and the portal and billing read as two separately documented products. As of July 2026 we found no single documented signup-to-plan-to-payment-to-key flow. On Farther Shore, that flow is the portal's core loop.
Per Kong's pricing page: $20 per million metering events plus 0.4% of billing volume, sold as an add-on, with the Konnect gateway (Plus tier) priced separately. Farther Shore's platform plans are public on our pricing page. According to G2 reviewers, common Kong themes include a learning curve and pricing that can be high for smaller teams.
Sources: konghq.com/pricing
| Capability | Farther Shore | Kong Konnect + OpenMeter |
|---|---|---|
| Gateway for your API | Yesedge keys · plan limits | Yesthe most battle-tested in the industry |
| Usage metering | Yesat the edge | Yesanalytics + OpenMeter |
| Billing engine | Yes | YesGA Dec 2025 · prepaid credits Jul 2026 |
| Settles money | Via Stripebuilt into the flow | Nobring your own Stripe key |
| Subscriber portal | Yessignup · checkout · keys · usage, one flow | Partialdev portal + generated Stripe Checkout link |
| Hosted docs | Yes | YesOpenAPI API docs |
| Pricing as code | Yesplans + prices in one TS file | PartialdecK/Terraform for gateway config; billing plans — none found |
| Agent operability | YesCLI + MCP | Partial |
| Self-hosted data planes | No | Yes |
| Published pricing | Yespublic platform plans | Yes$20/M events + 0.4% of billing volume (add-on) |
Choose Kong when the gateway itself is the hard requirement: self-hosted data planes, hybrid deployment, enterprise API-ops governance across hundreds of services, and the most battle-tested gateway infrastructure in the industry. If Konnect already fronts your APIs, adding Kong's metering where you already operate can be the shorter path.
FAQ
Only at the edges. For pure gateway infrastructure — self-hosted data planes, enterprise API-ops governance — Kong is deeper. Farther Shore is a business platform whose gateway is one output of a compiled TypeScript business file, next to billing, portal, and docs.
No. Kong's setup guide has you supply your own Stripe API key; Kong generates the catalog, rating, and invoices while Stripe stores cards and collects payment.
Per Kong's pricing page: $20 per million metering events plus 0.4% of billing volume, as an add-on — with the Konnect gateway tiers priced separately.
Kong's decK and Terraform tooling covers gateway and dev-portal configuration as code. As of July 2026 we found no evidence of declarative coverage for billing plans and prices. On Farther Shore, plans and prices live in the same TypeScript file as the gateway rules.
Kong's Dev Portal is real and branded, with self-serve app registration and OpenAPI docs. Checkout, however, is a generated Stripe Checkout link, and we found no single documented signup-to-plan-to-payment-to-key flow as of July 2026.
Keep comparing