Single listing
For one business with a selectable duration.
1 month
All amounts exclude VAT.
- Publish 1 listing
- Anonymous or visible contact details
- Save as draft possible
No payment before publication.
For one business with a selectable duration.
1 month
All amounts exclude VAT.
No payment before publication.
For regular sellers with several listings.
3 active listings
Billed yearly. All amounts exclude VAT.
No payment before publication.
Selling source code takes more than listing functions. Buyers want to understand language, architecture, rights, repository, documentation, dependencies, tests, security and handover. A clear listing shows whether the code is usable, maintainable and genuinely transferable.
The listing should explain which application, library, API, platform, app or internal solution is built on the source code. Languages, frameworks, modules, database, interfaces, functions, users, development status and current use help buyers understand technical substance.
It should state who owns the code, whether third parties contributed, which open source licenses, libraries, assets, API services or contracts exist and whether rights can be transferred fully. Open ownership or license questions should remain visible.
Tests, code quality, security status, known bugs, technical debt, deployment, hosting, CI/CD, documentation, access and maintenance effort strongly affect value. Sellers should explain what already runs in production and what still needs development.
If the offer includes a complete product with operation, customers or a business model, Sell software may be more precise. If the code mainly belongs to a mobile or web app, Sell app often describes the offer better.
It means offering a codebase with rights, repository, documentation, dependencies, access and defined handover terms.
Languages, frameworks, functions, architecture, repository, rights, licenses, dependencies, tests, documentation, deployment and handover are important.
Yes. Buyers need to know who owns the code, which rights are transferable and which licenses or third-party contributions exist.
Yes. They can affect use, distribution, code publication and obligations after handover.
Documentation, Git history, tests, architecture, deployment instructions, screenshots, demo access and dependency lists are useful.
Yes, but the listing should explain the real development status, what works and what effort is still required.
Software is more suitable when the offer includes a usable product, users, revenue, support or processes beyond the code itself.
No. company.ch helps sellers publish the listing and receive inquiries, but it does not replace technical, legal or commercial review.