For automation agencies and freelancers

Your client gets a link. You keep the code.

Publish the automation you built for a client. They fill in a form, press RUN and get the files.

Three real runs

Public Widgets on Abyss, and the runs their pages show.

For a finance client

A 130-page annual report goes in. One dashboard comes out, and each figure links to its page.

Your client gives
The PDF to analyseTSLA 10K.pdf
Ƀ 100 a run · about $1
Financial Data Extractor: what its run makes
Your client getsinteractive_dashboard.html
Open the real run

Financial Data Extractor

The work is done. The handover is the hard part.

You built it on your machine, or in your own n8n. Now your client wants to use it.

  • Whose account does it run in?

    Abyss runs it.

    Each run gets its own machine. Your client needs only a browser.

  • Who holds the API keys?

    You do.

    They stay in the Widget's Environment variables, and your code reads them on each run.

  • How does the client use it, while the work stays yours?

    With a Private Link.

    Your client sees the form and the outputs. The code stays with you.

  • How do you charge when the use changes?

    Your choice, for each client.

    By the run, by the month, or in your own invoice.

  • How do you learn that a run failed?

    Your Bell rings.

    A failed run costs your client nothing.

Pro

What your client opens

With Pro, each client gets a named link. It opens a page with your logo, your Studio's name and the one Widget.

Four steps

  1. 1

    Publish it as a private Widget.

    Upload the project. Your API keys go in Environment variables.

  2. 2

    Send your client a Private Link.

    With Pro, one named link for each client.

  3. 3

    Choose who pays.

    By the run, by the month, or you.

  4. 4

    Show your client the month.

    Pro keeps a record of every run, and a summary of each month.

If you built it in n8n, make it a Python project first. The Guide shows how.

Who pays, and what you get

You choose for each client. Pro, at $24 a month, adds the second and the third way.

By the run

Your client pays

about $5

You withdraw

$3.50

for one run at Ƀ 500

  • Your client buys Byssium: 100 for about $1.
  • A failed run costs nothing. Abyss gives the Byssium back.
  • You withdraw $0.70 for every 100 Byssium.
By the monthPro

Your client pays

$200

You get

$170

each month

  • You set the price, from $5 to $5,000 a month.
  • Your client pays by card. Every run they make on the website that month is in it.
  • Abyss keeps 15%.
You payPro

You pay for Pro

$24

You keep

your invoice

in full

  • Your client opens the link with no account.
  • Their runs are your own runs, so they cost you no Byssium.
  • You charge your client in your own invoice, for example a fixed monthly fee.

Each run uses your keys, so your AI provider bills you for it. Put that cost into your price.

Your next client gets a link.

The whole job, step by step: Deliver an automation to a client and charge for each run