Help & FAQ

How do I place an order?

Browse gigs, pick a tier (Basic / Standard / Premium), confirm at /orders/new, and fill out the requirements form. Funds go into Stripe-managed escrow and the delivery clock starts the moment you submit requirements.

What happens if the prompter is late?

You can request a revision or open a dispute. In the Resolution Center a late order can end in a full refund or a mutual cancel.

What if I don’t respond to a delivery?

Auto-accept kicks in 3 days after delivery. Funds release to the prompter. This protects prompters from buyer ghosting.

How are revisions counted?

Each tier has a fixed number of revisions baked into the price. Beyond that, you and the prompter work it out on the order, or you place a new one.

Can I cancel an order?

Mutual cancellation is always possible. Unilateral cancellation goes through the Resolution Center.

Which environment should I choose?

There are four, and they differ in what can be proven afterwards — not in convenience. An Orquesta project is the only one where the platform counts the prompts itself, so it is the only one that can settle a disagreement without either of you having to be believed. Your own repository leaves the record in commits, branches and pull requests: checkable by both of you, metered by nobody. A seat in a closed tool (Cursor, Lovable, Replit, v0, Bolt) leaves a record nobody outside that tool can read — us included — so it is priced by the hour and builds no verified history. And “they work on their own setup” hands over nothing at all: the platform sees the delivery and nothing else.

How do I grant access, exactly?

The order page walks you through the environment you picked, step by step, and the same lists are further down this page. The shape is always the same: invite them with their own email address, give the smallest role that lets them work, scope it to the one project or repository you hired them for, mark it handed over on the order, and remove it yourself at the end for anything we did not grant.

Do I ever have to send a password or an API key?

No. Nothing in this flow needs one, and Derplins will never ask you for one. If a project needs a secret value to run, put it in the repository’s own secrets store and tell your Derplin the name of it, never the value. If anyone asks you for a credential — in the order chat or anywhere else — that is not us: do not send it, and email support@derplins.com.

When does the delivery clock start?

When both of you have confirmed the handover on the order: you mark that you gave access, your Derplin marks that they got in. One side’s word is exactly the handover that gets disputed later, so neither mark alone starts anything. Until then the environment sits as “not handed over yet” and the clock is stopped.

How do I take the access back?

On an Orquesta project we remove the membership automatically when the order closes, and you can end it yourself from the panel at any moment. Everywhere else the access lives in your account and only you can remove it — do it in the tool, then mark it on the order so the date is on the record. The panel never tells you we can take back something we did not grant.

What is on the order page?

One order, one screen: its status and dates, the requirements you submitted, the environment panel (choose it, hand it over, get it back), the meter while the work runs, the delivery when it arrives, and the buttons to accept it, ask for a revision or open a dispute. The message thread for the same order lives under Messages.

What is the meter counting?

Prompts that actually passed through the environment you handed over — a number neither of you writes. Watch it early: zero prompts against a live environment does not mean the work is cheap, it means the prompts are not going through that environment, and at acceptance an order like that bills nothing. That is fixable while the order is open and only an argument afterwards.

Where do I talk to the other side?

On the order’s message thread, and it is worth keeping it there rather than moving to email or a DM: the thread and the delivery are what the Resolution Center reads if the two of you end up disagreeing.

What does the Resolution Center actually do?

It turns a disagreement into a decision. Either side opens it on the order and proposes one of exactly three outcomes: a full refund to the buyer, release to the prompter, or a mutual cancel. There is no fourth, and there is no partial number to haggle over.

Where do I find everything else?

Your dashboard lists your orders on both sides. Payouts holds your earnings and clearance schedule, Settings holds your account and payout method, and Levels explains how the nightly recomputation works.

When do I get paid?

When the buyer accepts (or 3 days auto-accept), your earnings — the package price minus the 15% Derplins take — are transferred to your payout account: your Stripe balance, or your Notlogin wallet in USDC, matching how the order was paid. Clearance ranges from 14d (New) to 1d (Top Rated) based on your level.

How do I avoid going off-scope?

Stay inside the repo, branches, and paths the buyer named in the requirements. Nothing on Derplins enforces that for you — if the work needs more than they gave you, ask on the order before you touch it.

How do levels work?

Levels recompute nightly from rolling-60d metrics: orders, earnings, rating, on-time rate, cancel rate. See /levels for the full breakdown.

How are disputes resolved?

Either side opens the Resolution Center on the order and proposes one of three outcomes: full refund to the buyer, release to the prompter, or mutual cancel. Those are the only three. What both sides argue over is the delivery and the messages on the order.

What if the prompter leaks my data?

Email support@derplins.com and open a dispute on the order. Be clear-eyed about this: Derplins does not sit between the prompter and your environment, so nothing on our side detects or blocks it. Grant the narrowest access that lets the work happen, and revoke it when the order closes.

How do I report abuse?

Email support@derplins.com or use the Resolution Center on the order.

An Orquesta project

What you grant on an Orquesta project

1. Pick the project above. We add your Derplin to it as a member — you do not send anything by hand.
2. They get a member seat on that project only: they can run prompts in it and see its history. They cannot touch billing, your other projects or your organisation settings.
3. Leave your provider keys where they are. The project’s agent already holds what it needs to run, so there is nothing for you to paste anywhere.
4. When the order closes we remove the membership automatically. You can also end it from this panel at any moment, without asking anyone.

• ✕Never paste an API key, a password or a token into the chat — the seat is the access, and it is enough.
• ✕Never hand over your own Orquesta login: a member seat can be revoked, an account cannot.

Your repository

What you grant on GitHub

1. Open GitHub and invite your Derplin to this repository as a collaborator with Write access. Write is enough to deliver; Admin or Owner is not needed for any order.
2. Scope it to the one repository. An invitation to the whole organisation hands over every other repo in it as well.
3. Keep your protected branches protected. They push a branch and open a pull request, which is also what makes the work checkable afterwards.
4. If they need a secret value to run the project, put it in the repository’s own secrets store (GitHub has one) and tell them the name of it. Never the value itself.
5. Come back here and mark it handed over. Your Derplin confirms they got in, and both marks are kept with the order.
6. When the order closes, remove the collaborator in GitHub yourself — we have no access to your account and cannot do it for you — then record it here.

• ✕Never share your GitHub password, or a personal access token that belongs to you.
• ✕Never grant Admin or Owner rights for a single order.
• ✕Never commit a credential to the repo so they can read it there.

A seat in your Lovable / Cursor / Replit account

What you grant in Cursor

1. Open Cursor and invite your Derplin to your team or workspace using their own email address, so the seat is theirs and not a shared one.
2. Give the smallest role that lets them work — member or editor. Never owner, admin or billing.
3. If Cursor lets you scope an invitation to a single project or workspace, scope it to the one you hired them for.
4. Come back here and mark it handed over, so the date is on the record. Your Derplin confirms they got in.
5. When the order closes, remove the seat in Cursor yourself and mark it here. Nobody outside Cursor can see that seat — not us — so this record is the only one there is.

• ✕Never share your login. It breaks Cursor’s terms, it cannot be revoked without changing your own password, and afterwards nothing tells your work apart from theirs.
• ✕Never move billing or ownership to them, not even temporarily.
• ✕Never paste an API key of yours into the chat so they can use it from their own account.

Nothing — they work on their own setup

What you send when nothing changes hands

1. Send the brief, the files and any sample data through the order chat, so what was asked for stays with the order.
2. Strip credentials out of what you send. If a value is a secret, it is not part of a brief — replace it with a placeholder and say what it is for.
3. Agree what the delivery looks like — a zip, a repository, a link — before they start, because the platform sees the delivery and nothing else here.

• ✕Never send a password, an API key or a .env file so they can "test it properly". If the work truly needs your environment, choose one of the other options instead.