Terms of Service

What the platform does, and does not, do

We evaluate developers on two things — fundamental engineering ability and how well they use AI coding tools — and we match the ones who clear both against briefs clients bring us, for a project, for part-time hours, or for a full-time role alongside your own team. That is the whole service. We are not a staffing agency that employs the people it places, and we do not take responsibility for your roadmap the way a delivery agency would. Once a match is made, you run the work.

Nobody becomes anybody's employee

A developer matched through this platform works as an independent contractor. Not your employee, not ours. A match under these terms does not create employment on either side, in either direction — that is true whether the engagement lasts a week or two years. If your own jurisdiction imposes particular rules on how a contractor relationship has to be structured, raise it while we are setting the engagement up, not afterwards, and we will build the paperwork around it.

Day to day, you are in charge: you set the priorities, you review what gets built, you decide what ships. A contractor relationship does not mean hands-off oversight — it means the developer is not on anyone's payroll.

Three shapes of engagement

A project engagement is scoped and quoted against a defined piece of work with a start and an end. Part-time and full-time augmentation add a matched developer to your team for an agreed number of hours a week, running until either side gives notice rather than to a fixed finish line. Which shape, how many hours, and what overlap is expected all get written down before the developer's first day, not assumed.

Money

Every rate is quoted in US dollars, per developer, set by the engagement shape, the stack and the seniority the role calls for. It is agreed in writing before work starts and does not move mid-engagement unless both sides sign off on the change. Ongoing engagements are invoiced monthly in arrears through the platform; project work is invoiced against milestones agreed up front. Bank fees, currency conversion and any tax properly owed in your jurisdiction sit with you. If payment stops, we can pause the engagement after giving notice — we would always rather flag a payment problem early than let work continue unpaid without a word.

Ending an engagement

A project runs to whatever scope was agreed. Ongoing augmentation carries a minimum term and a notice period, stated in the engagement paperwork, that binds both sides equally — it exists because a developer has turned down other work to keep the hours free for you, not as a lever to trap an unhappy client. Notice has to be given in writing.

If the match is wrong

A developer who is not working out gets replaced at no extra charge, provided the issue is raised in the first two weeks of them starting. From the moment you raise it, billing for that developer stops. Tell us specifically what went wrong — pace, communication, AI-assisted output that did not hold up — because a vague complaint produces a vague replacement. You interview and choose the replacement the same way you chose the original; nobody gets substituted on you without a say. The guarantee covers fit and capability, not a change of heart on your side about the role or the project, and it is not a refund on hours already worked. The full conditions live on the replacement guarantee page.

Hiring a matched developer permanently

This is the clause every marketplace gets asked about, so here it is stated directly rather than left in small print. For the length of an engagement, and for an agreed stretch afterwards, you do not go around the platform to engage a developer we introduced you to — directly, or through some other intermediary — without talking to us first. The same runs the other way: we will not poach your own staff.

None of that is designed to trap anyone. Wanting to hire a matched developer for good is a completely normal outcome, and we treat it as a conversation, not a violation. It is settled with a buyout fee that reflects what went into matching and vetting that person, usually stepping down the longer the engagement has already run. We will never stand between a developer and a genuine permanent offer. What the clause actually stops is the arrangement happening quietly around us, which is the version that damages trust for everyone involved.

Keeping things confidential

Whatever either side learns about the other during an engagement — your codebase and credentials, our assessment material, a matched developer's personal information — stays confidential, gets used only for that engagement, and only reaches people who need it and are bound by the same duty. A matched developer is under that same obligation, so it reaches the person actually reading your code, and it outlives the engagement itself. We will sign your NDA, or offer a mutual one, before any detailed discussion of your systems.

Who owns what gets built

Work produced for you during an engagement belongs to you. That assignment runs through the matching agreement and the developer's own commitments, so there is no gap where a contractor could later claim rights over it. Three normal exceptions: open-source pieces keep whatever licence they already had, third-party services stay governed by their own terms, and a developer's general skills and know-how — including how to use AI tools well, which was not learned from your codebase — remain theirs to take to the next engagement. Your code, your data and anything built specifically for you do not travel with them.

Personal data your systems hold

If a matched developer ends up handling personal data belonging to your own users, you are the one who decides why and how it gets processed — that responsibility does not shift to us. Flag which regime applies to you while we set the engagement up, including whether a formal data processing agreement is needed, and we will build around it. Access to your systems is something you grant, scope and can revoke, on your terms. What this website itself collects through its own forms is a separate matter, covered in the privacy policy.

What vetting cannot promise

Here is the part we will not dress up. Screening on two axes lowers the odds of a bad match considerably; it does not remove them. We cannot promise a specific developer will be free at a specific time, that a project lands on a date you picked before scoping it, that AI-assisted work always beats the alternative on speed, or that a commercial outcome follows automatically from a good match. Those depend on your own requirements, your architecture, decisions made along the way, and plenty that is outside anyone's control. What the vetting genuinely buys you is a much lower chance of the one failure it is built to catch — a developer fast with an AI tool who does not catch what it gets wrong. It is not a guarantee against every other way a project can go sideways, and we will tell you when a target looks unrealistic before you commit to it, not after.

Liability

Neither side answers to the other for indirect loss, lost profit, lost revenue, lost savings, lost opportunity or lost data, whatever the cause. The most either party owes the other in connection with an engagement is capped at the platform fees paid in the period the agreement specifies. None of this limits liability that cannot legally be limited — fraud, or death or injury caused by negligence, are never capped.

When an engagement ends

Either side can end an engagement on the agreed notice, immediately for a serious breach that is not fixed within a reasonable time after being raised in writing, or if the other party becomes insolvent. On the way out: fees already earned stay payable, system access gets revoked, the developer hands back anything unfinished or undocumented, and confidentiality and IP obligations keep running exactly as before.

Using this website

Everything on hirevibecoders.co is informational. Nothing here is an offer you can simply accept, and no contract exists until an engagement agreement is actually signed. Please do not put credentials, API keys or anything sensitive into a form on this site. Content here can change at any time without notice.

A few standard clauses

A signed engagement agreement and any statement of work under it override this page wherever the two disagree. Neither side can hand an agreement off to someone else without the other's written consent, except to a genuine successor of the whole business. If one clause here turns out to be unenforceable, everything else still stands. Not enforcing a term once does not waive it for later. Neither side is on the hook for failing to perform because of something genuinely outside their control.

Governing law

Which law applies and where disputes get heard is set out in your signed engagement agreement, agreed rather than assumed, because clients are spread across enough jurisdictions that no single default suits everyone. Absent an explicit choice, the law where Hire Vibe Coders operates applies. Either way, both sides agree to raise a disagreement directly and try to sort it out in good faith before anyone files anything.

What this page is

This is a plain description of how engagements actually work, written by the people running the platform — not legal advice, and not a substitute for a lawyer who knows your own jurisdiction. Wherever it conflicts with something you have signed, what you signed wins.

Contact

Questions before you sign anything: info@hirevibecoders.co, or call +91 63530 74980, Monday to Friday, 10:00–19:00 IST. The contracts and IP page covers ownership, NDAs and direct hire in more everyday language.