Everything a software business runs on — the entire lifecycle, from billing and access to customers and operations. Programmable end to end, so an agent can run it.
Capabilities
Selling software means building a second product nobody asked for: auth, API keys, rate limits, metering, billing, checkout, a customer portal, docs. Farther Shore ships all of it as one system with one source of truth — so the limits you enforce, the usage you meter, and the invoices you send can never drift apart.
Gateway
Your API sits behind a gateway that checks keys, enforces plan limits, and rate-limits every request. Customers mint, scope, and rotate their own keys from the portal — you never build auth again.
Pricing
Free tiers, subscriptions, usage-based pricing, prepaid credits — declared in a business file that lives next to your code, gets reviewed in a PR, and is versioned in git. Change the file and the change ships everywhere at once: gateway, billing, portal, docs.
Portal
Every product gets a hosted portal in your brand: sign-up, checkout, docs, usage dashboards, and key management. It's live from the moment you publish — no frontend sprint required.
Billing
Usage is metered at the edge and settled through Stripe — subscriptions, overage, credit burn-down. Every call is accounted for exactly once, so the invoice always matches the meter.
How it works
Four steps, one afternoon. No billing integration to write, no auth service to run, no portal to design — your API stays exactly where it is, and the business gets built around it.
01
Point Farther Shore at the backend you already run — any HTTP API, hosted anywhere. It keeps running untouched; the gateway goes in front of it.
02
Describe your plans, prices, meters, and limits in business.ts. The compiler turns that one file into an enforceable contract.
03
One publish compiles, verifies, and deploys the whole surface: gateway rules, Stripe plans, the customer portal, and your docs — from the same source of truth.
04
Customers sign up, subscribe, and start calling. Usage meters, limits enforce, invoices settle — your dashboard shows revenue and customers, not plumbing.
Programmable business
Pricing, plans, limits, and entitlements aren’t dashboard settings — they’re code in your repo. Version a price change, review it like a pull request, ship the old file if you change your mind. And because the whole business is a program, software can run it: every operation is exposed over the CLI and MCP.
Use cases
Usage-based, subscription, prepaid, or free with limits — and any mix of them. If your software serves requests and deserves revenue, it fits.
Connect the endpoint, write the business file, publish. Plans, keys, metering, billing, and your customer portal are live before the day is out. And because the whole business is code and contracts, it’s already operable by the next wave of customers: agents.