Developer workflow

Developers build Worker and Web apps off-platform during in_progress. Velcio stores the final delivery as a ZIP artifact (uploaded directly or imported as a GitHub snapshot).

Steps

1. Choose a username at sign-up (required). Buyers assign you to projects by username; your email is not shown to buyers.
2. Add a marketplace photo (optional) under Developer profile. Your avatar appears on /developers when you are listed. You can also add optional GitHub and website links there. A profile photo is required before marketplace opt-in. You can list without Stripe Connect; Connect is required before you accept paid work or submit proposals.
3. Browse Open projects and submit a priced proposal when a listing fits (see Proposals below). If the buyer accepts your proposal, you are assigned at that price; wait for them to fund, then accept the assignment as usual.
4. Accept an invite when a buyer invited you by email before you had a Velcio account. Open the link, sign up or sign in with that email, then accept the assignment.
5. Review pricing on the project Pricing section for directed hires. If the buyer set an opening offer, accept it or send a counter-offer. If they requested a quote, submit your price first. Open-listing work is already priced when your proposal is accepted.
6. Accept the assignment within 48 hours of buyer payment authorisation. Choose Python or Node.js and a supported runtime version when you accept.
7. Declare required env vars on the project page while in_progress. Apps that need a database often use DATABASE_URL (quick-add from suggestions); add only the keys your code actually reads (for example OPENAI_API_KEY). Save early so the buyer can configure secrets before you submit.
8. Work off-platform during in_progress. You do not receive buyer secret values.
9. Submit delivery when ready: upload a ZIP or import a GitHub repo snapshot (see GitHub import below). Confirm required env vars in the submit form. Explicitly choose Worker (long-lived process, no public URL) or Web (HTTP on *.velcio.app). Anything that needs inbound webhooks or a public HTTP endpoint must use Web. Web apps must listen on env PORT (Velcio sets 8080) and implement GET /healthz in the app (HTTP 2xx; Velcio does not add this route). Velcio validates, builds, and deploys.
10. Verify the running delivery after Velcio builds and deploys. For Web apps, open the public URL shown on the project page (and in Verify delivery) and confirm it works before you continue. Check logs, redeploy, rebuild, or submit a corrected ZIP/GitHub snapshot while the project stays submitted. Verification deploys use the same continuous runtime cap as buyer review (default 120 minutes per run); restart opens a new window. If a deploy fails (for example missing secrets), the project returns to in_progress; after a successful retry it returns to submitted so you can confirm.
11. Send to buyer for review when you are satisfied. Buyer review and the review deadline start only after you confirm delivery. Confirming delivery also starts a fresh buyer review runtime window.
12. Handoff happens when the buyer accepts. You assign full ownership of the delivered source code to the buyer and may not reuse it for other clients or projects unless the buyer agrees separately outside Velcio. Your project access is revoked after completion. You receive a payout timing email when payment is captured.

Proposals

Browse public listings at Open projects. To submit a proposal you need developer mode, Stripe Connect complete, and availability turned on for marketplace work.

• Include price (£), pitch, answers to any listing questions, and optional estimated days.
• You can update a pending proposal or withdraw and submit again later.
• The listing shows whether the buyer has viewed your proposal.
• If the buyer accepts, you are assigned at that price (no directed price negotiation). Wait for them to fund, then accept the assignment within 48 hours.

Directed hires (username or email invite) still use the project Pricing section for opening offers, quotes, and counters.

GitHub import

Use Import from GitHub on primary delivery and revision submit when you prefer a repo snapshot over uploading a ZIP.

1. Open Settings → Developer profile → Connected GitHub.
2. Connect (or add / reinstall) the Velcio GitHub App on your user or org account. Unlink from the same page if needed.
3. On the project Delivery (or revision) form, choose Import from GitHub, pick repository and branch / ref, confirm the resolved commit, then submit with runtime and env vars as usual.

Import is a one-time snapshot of that commit. Pushing later does not redeploy. Private and public repos work if the install can read them. If the environment has not configured the GitHub App, the UI says import is unavailable.

The optional GitHub profile URL on your marketplace profile is only a public link; it does not connect the App.

Layout rules: Delivery format.

Payouts

Connect your Stripe Express account under Developer profile before you accept assignments, submit proposals, or expect transfers. You can opt into marketplace discovery without Connect first. See Developer payouts for hold timing.

Use the Pricing section on draft projects to accept or counter-offer until you and the buyer agree on a price.

Use the Discussion section on the project page to coordinate at any stage (before and after funding).

Delivery format

ZIP or GitHub snapshot layout: Delivery format.
Web HTTP apps (PORT, app-implemented /healthz): Web delivery format.

Common problems: Troubleshooting.

Revisions

Buyers may fund revision jobs on completed projects. You receive scoped upload/redeploy access until the revision is accepted or access expires. Submit a corrected ZIP or GitHub snapshot for the revision preview. After deploy succeeds, verify the running delivery and confirm revision delivery before the buyer can accept. When the buyer accepts a revision, you assign ownership of the updated delivery on the same terms as the original handoff and may not reuse that revision work elsewhere without separate buyer consent.