Building a support system on open source with a freelancer — who owns the rights?

Pay close attention to AGPL. If they write code directly into the AGPL core, that code might get swept under AGPL too. If you have them architect the custom modules as separate services communicating with the core strictly over an independent API, you'll be on much firmer ground regarding ownership.

We had a support system built for $6,000 two years ago on a similar setup. Because we didn't specify code ownership in the contract, the developer asked for an extra $2,000 just for a simple API update. If you don't get the rights transferred upfront, that system will end up costing you way more than commercial software in a few years.

Set up a private Git repo under your company immediately and give the dev write-only access. Code should flow into your server every single day. Never let them say "I'm keeping it on my local machine I'll dump it all when we're done."

Is the developer writing a new panel from scratch, or integrating reusable libraries they already built for other clients? If they're using pre-existing shared tooling, licensing that makes sense; but anything built from scratch using your $7,500 must belong entirely to you.

Under US law regarding the "Work Made for Hire" doctrine, IP created by independent contractors does not automatically transfer to the hiring party without an explicit written assignment. Having an express assignment of rights in your contract is a legal necessity to avoid losing title.

dont let this guy keep the rights to custom code you paid for. tomorrow he'll turn around and sell the exact same module to your competitor, and you'll be stuck paying him every time you need a single line of code changed.

The golden rule when working with software devs: if that developer disappears off the face of the earth the day the contract ends, another engineer must be able to take over within 24 hours based on the docs and access provided. Don't sign any contract that doesn't guarantee this.

edit: fixed a few typos.

I'd appreciate it if you shared the outcome.

There's a trap here let me mention it. When you try to change everything at once, nothing settles.

If you post the result here, it will help others too.

Thanks, that was the answer I was looking for. When we decide without measuring, we always end up in the same place.

Just leaving this note, it might be useful.

Three different views emerged, they all complement each other. Mistakes made on the open source code ownership side are usually reversible but expensive.

Are you looking for a partner or a co-founder? They are two different things. That's all, sorry if I went on too long.

I partly agree, partly disagree. Partnership isn't a decision to make without working together first.

That's all, sorry if I went on too long.

Three different views emerged, they all complement each other. Do a small three-month project before talking stocks, so you see each other.

Good luck with that.

I was thinking the same thing. The only thing separating friendship from partnership is a written contract.

Thanks a lot, I'll try it today.

Same here. Taking notes for two weeks yields better results than a six-month estimate.

Of course, it varies if your situation is different.

i agree.

Thanks for writing this, that's the right way. The only thing separating friendship from partnership is a written contract.

Just leaving this note, it might be useful.