Three things your customers keep asking you for — a site that exists at an address, a publishing cadence nobody has to staff, and someone to take the first call. Embed them in your own product. You keep the brand, the relationship and the invoice.
Your user describes a page. One POST starts the run and what comes back is an HTTPS address — bucket, hosting, certificate and DNS all inside the run. Revisions are listed, rollback is an endpoint, and the bytes sit in a cloud account you own.
Scheduled runs research the subject, draft it in a voice you define, generate the hero image and open a pull request. Nothing self-publishes — a human still merges, which is what makes it safe to put a customer's name on.
See what it takes to run →Your lead books a call. An agent joins it already briefed on who they are and what they asked about, has the conversation, and leaves a transcript behind. Video meetings — Google Meet and Kontur Talk.
See what it does and doesn't do →You authenticate as yourself, with a token you issue from your own settings — nobody mints one for you and nobody is in the loop when you rotate it. Cloud credentials are stored against your organisation and resolved server-side at the moment a tool runs, so there is no credential on our side that can reach another partner's infrastructure. A read for an organisation that is not yours returns not found, never forbidden — we do not confirm that the other tenant exists.
That is the whole setup. The dispatch is the same generic endpoint every Forge run uses — one call returns a run id, you poll it — so there is no bespoke API you would be the only caller of, and no SDK to wait on. The token authorises everything your organisation can do, so it lives in your backend and never reaches an end user.
Usage is attributed to the organisation that ran it, priced against a rate card, drawn from a credit balance with an allowance gate in front of it. So you can see what each customer costs you before you decide what to charge them. Bring your own model keys if you would rather pay the provider directly.
There is no partner-branded console. Your customers never see a Forge dashboard because they never get one — everything reaches them through your product, which suits an embedded feature and does not suit reselling a login. Voice is video meetings, not telephony — nothing here answers a phone number. Site deployment targets one cloud's storage, CDN and DNS today; the workflow shape is not tied to it, but the other adapters are not written yet. We would rather you read that here than discover it in week two.