Code with context
Documentation, tests, build instructions and development history can help make a codebase understandable.
For the folders full of good work
Old projects. New possibilities.
There might be more in your archive than something to back up.
Past codebases, tools, documentation and development history can tell a useful story together. Goodwattle reviews selected materials for potential purchase or licensing opportunities.
Explore my project archiveNo obligation. No code upload required to start.
A fresh look at the back catalogue.Australian teamSelected work you ownClear terms before handover
Good work has more to give
The work between releases counts too.
An archive is more than a finished build. The decisions, tests and supporting materials help explain how a project came together.
One project or several
Begin with a representative project. If you have a wider portfolio, mention it in your description.
A considered handover
We agree the selected materials and exclusions before delivery. Start with an overview, not a full archive upload.
A good place to start
Sounds like
your kind of work?
Describe the kinds of projects in your archive, then pick one example to start with.
- Past games, software projects or internal tools
- Original documentation, tests or development history
- An owner who can explain the archive and its rights
A description is plenty for the first step. Please leave out private code, passwords and personal data.
Tell us what you’ve gotA little look. A clear next step.
From old work
to a new conversation.
- 1
Tell us about it
A short appraisal covers your project and how to reach you. A link or small, non-confidential sample is optional.
- 2
Explore the fit
A real person reviews your overview. We discuss the opportunity and arrange confidentiality before a detailed review.
- 3
Consider an offer
If there’s a fit, we put the scope, rights, intended uses and payment in writing. You decide whether to proceed.
A purchase. A licence. A possibility.
A purchase can transfer agreed rights. A licence can let you keep ownership while permitting specific uses, including AI research, training or evaluation. We can discuss a fixed payment, revenue share or ongoing arrangement where suitable. Nothing is sold or licensed by sending an enquiry.
Before you say g’day
Good questions.
A little clarity
goes a long way.
Should I upload the whole archive?
No. Start with a non-confidential description of what it contains. Any detailed review and full handover are arranged separately.
What if the archive mixes client and internal projects?
Separate the projects you control from work owned by clients or other parties. Describe only materials you have authority to offer, and flag any uncertainty.
Is documentation useful without a complete project?
It may be, depending on what it covers, the associated materials and the intended use. Explain what remains so we can assess the fit.
What happens after I enquire?
We review your overview and follow up by email. If there is a fit, we discuss confidentiality and any detailed review, then propose the materials, rights, permitted uses and payment in writing. An enquiry is not a commitment to sell or license.
How much could my work be worth?
It depends on the quality, scope, rights and fit of the materials. This is a personal review, not an instant valuation. Not every project receives an offer, and any amount and payment timing are agreed in writing.
What will the materials be used for?
Agreed uses can include AI research, training and evaluation. The agreement sets out the permitted uses and any further licensing before handover. Your initial enquiry does not grant a licence.
Let’s see what’s possible
You did the hard work.
Let’s take a look.
Start with a few details. We’ll explore what could come next.
Explore my project archiveA friendly appraisal. No obligation to accept an offer.