Work internally
Design, knowledge and workflows run on your infrastructure. Use your own models or providers you choose. A connection to the c9n community is not required.
BUILDING TOGETHER
The community starts with people: discussing processes, sharing experience and improving c9n together. As an optional extension, we want to make spare GPU capacity useful to others.
Design, knowledge and workflows run on your infrastructure. Use your own models or providers you choose. A connection to the c9n community is not required.
The idea: share selected models on your GPU when capacity is available. You decide who can use them, when and within which limits. Sharing should be pausable at any time.
Another team could send an explicitly approved model request to your server – or you could use theirs. Not every task needs the largest model.
The plan is a small cloud gateway for coordination. Internal users, projects and knowledge stay in your installation. A community request sends its selected inputs to the gateway and the chosen model operator. Participation is intended to be off by default.
Our credit concept: providing confirmed computing work earns credit towards model requests from others. Model, effort and quality should matter. We will develop the rules and accounting with the community; a usable credit system is not available yet.
Today: The central gateway foundation is deployed. GPU sharing between independent installations and credits are not publicly available yet. Internal operation remains independent.
WHY c9n?
c9n stands for cooperation. There are exactly nine letters between the first c and the final n in “cooperation”. That gives us c9n.
The name reflects our purpose: people, knowledge and AI working together. Within your organisation – and, if you choose, with a community sharing experience, ideas and spare computing capacity.
Explore our brand →Pronounced C-nine-N