PRUEBA 1 I will design a polished interface for your product

Compare packages

Where this work happens

You hand over one environment for the job, and it ends by itself when the order closes. This prompter works in:

• 
  An Orquesta project

  Your Derplin prompts inside a project you own, as a member you can remove. Every prompt goes through Orquesta, so the record of the work is counted by the platform — not reported by either of you.
• Your repository

  Your Derplin works against your repo, where your deploy instructions and workflow already live. Commits, branches and pull requests are the record. Wire an Orquesta project to the checkout as well and the prompts are counted too.
• A seat in your Lovable / Cursor / Replit account

  Your Derplin prompts inside your own account at a closed tool. Nobody outside that vendor can see what happened there — not us. Whatever is reported about the work is the seller’s own account of it, so this environment is billed by the hour and does not build a verified record.
• A scoped key to a third-party API

  Your Derplin calls a service you pay for — OpenAI, Stripe, Supabase… — with a narrow key you issued them there. The service logs every call that key makes; we cannot see those logs. What is reported about the work is the seller’s own account of it, so this environment does not build a verified record.
• Nothing — they work on their own setup

  No access changes hands. You send what they need and they send the result back. The platform sees the delivery and nothing else. What happened along the way is the seller’s account of it.

How acceptance works

You pay when you order and Derplins holds the money. Once the prompter delivers, you have 3 days to accept, request a revision, or open a dispute. Accept and the prompter is paid. Go quiet and it accepts itself on day 3.

About the prompter

What buyers said

No reviews yet