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.
A SIMPLE HELLOAbout 20 seconds
Where can we say g’day?
Leave your name and email and we’ll get in touch. You can tell us about your project next, if you like.
Your enquiry is already saved.
No obligation · No code upload neededOptional · About 2 minutes
- 1 The basics
- 2 Your work
- 3 Extras & send
GOOD POST, SAFELY SAVED
Thanks for the g’day.
Your enquiry is saved. We’ll follow up using the contact details you shared.
Your reference
A little bird, a good conversation
Have a yarn with Wattle.
Goodwattle’s AI helper · The humans follow up by email
Your chat is saved with your enquiry and emailed to Pasha, Pennie and Andrew. OpenAI helps Wattle reply. Please leave out passwords, personal data and confidential code. Wattle can explain things; a person reviews any offer.
You’re all done. If you have a moment, you can also tell us a little about your project. Nothing is sold or licensed by enquiring.
Past codebases, tools, documentation and development history can tell a useful story together. Goodwattle reviews selected materials for potential purchase or licensing opportunities.
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
Your name and email are plenty to start. Add project details if you like, or talk it through with us later. 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
Say g’day
Leave your name, email and an optional phone number. We save your enquiry straight away; project details and a small sample can follow if you like.
- 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.
A LITTLE CLARITY
Good questions.
Honest answers.
Your work. Your next chapter.
Let’s make the possibilities clear.
Something else on your mind?Book a friendly call (opens in a new tab)Say g’day by email
What kinds of projects are you looking for?
Anything from full games and prototypes to gameplay systems, shaders, animations, tools and plugins. We work with Unity, Unreal, Godot, Blender, Rust, TypeScript and more.
How much can I get paid?
Smaller projects can range from A$200 to A$10,000. Substantial company-owned codebases can be worth A$60,000 or more. Value depends on complexity, quality, contents, rights and fit. Every project is evaluated individually; these figures are possibilities, not guaranteed offers.
Does my project need to be finished?
No! We consider finished games, unfinished projects, game jams, university assignments, prototypes and work-in-progress builds.
What will my projects be used for?
Your code and project files may be used to train code-generation models that help developers with time-consuming tasks like shaders, animations, gameplay mechanics and other technical workflows, so more time can be spent on the creative work.
Do I have to give up ownership of my game?
No! We offer licensing arrangements where you can retain commercial rights and continue developing, publishing and selling your game. Outright purchases are also possible, with rights agreed separately.
Can I keep working on my game?
Yes, under suitable licensing arrangements. You can continue building and commercialising your game while licensing your existing work to Goodwattle.
How do I get started?
Share a brief description of your project, its tech stack, and ideally a GitHub link or demo. We’ll take a look and discuss what it might be worth.
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.
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.