Straight answers, short and honest. If yours is not here, email support (at) osinix.com.
Your key arrived by email, so check your inbox first. If it is gone, email licensing (at) osinix.com from the address you purchased with and we will send it again.
Yes, at any time. Payments are handled by Polar, our merchant of record; use the link in your Polar receipt email to manage or cancel, or email support (at) osinix.com and we will take care of it. Your engine keeps running until the paid period ends.
Change your plan in your Polar customer portal, linked from your Polar receipt email. Polar handles the price difference automatically. Once the change lands, we send you a new license key. Basic, Pro and Pro Max are the same program, so there is nothing to download or reinstall: put the new key in place and MCS runs at your new tier. If anything is unclear, email licensing (at) osinix.com and we will handle it with you.
On the single-user plans (Basic, Pro and Pro Max), yes. Run the engine with --deactivate on the current machine, then activate on the new one. If you no longer have access to the old machine, email licensing (at) osinix.com and we will free it. Details are in the Licensing Guide, in the guides package beside your download. An MCS Enterprise license is bound to its server and moves by a new license file from Osinix: send licensing (at) osinix.com the new server's machine ID.
The quickest route is a single account at OpenRouter or HuggingFace: one key gives you access to many models from many vendors. And local models need no key at all.
Put the OpenRouter model slug in the model field, for example deepseek/deepseek-r1 or x-ai/grok-4.3. You will find the slug on each model's page at openrouter.ai.
Set the endpoint to https://generativelanguage.googleapis.com and enter your key. MCS detects the Gemini protocol from the endpoint automatically. Example model: gemini-2.5-pro.
No. MCS is one self contained download: unpack it, run the installer, add your license key, and it runs. Cloud models need only their API keys. Local models work through the OpenAI compatible server you already run. MCS installs no libraries, no runtimes, nothing extra.
Choose Custom as the provider and point the endpoint at your provider's OpenAI compatible API. That is also how a local model server connects.
Yes. Go to the free trial page or email freetrial (at) osinix.com, and we will send you a trial license key and a download link.
Not today. MCS runs on Linux and macOS.
No. The engine runs natively on your machine and needs no GPU of its own. Cloud models run on their provider's hardware. Only if you run local models does your machine need what those models need.
Yes. Exactly one participant is the moderator, and the engine refuses to run without one. The moderator opens the session, steers the deliberation, and produces the final deliverable.
Yes, a lot. The moderator steers the whole session and, in directed mode, chooses who speaks on every turn. Give the moderator role to your strongest model.
Two participants, one of which is the moderator. The engine requires an agenda, at least two participants, and a moderator whose name matches a participant.
Yes. A fully local panel works, with no cloud account and no API keys if your model server does not require one. You can also mix local and cloud models on the same panel.
No. Your prompts, files, and results travel directly from your machine to the model providers you configure, or stay entirely on your machine with local models. The only thing single-user MCS sends to Osinix is a daily license check in containing your license ID, a machine ID, and the engine version. MCS Enterprise sends nothing to Osinix at all. No content, ever.
Cloud models need internet, local models do not. On the single-user plans (Basic, Pro and Pro Max), licensing allows thirty days of offline operation between check ins, so a fully local panel keeps working through network outages. MCS Enterprise never contacts Osinix: its license is checked on your own server.
Yes, really. Participants produce real files during the session, a document, a code file, even an image, and MCS hands each file to the other participants so they can read, critique, or build on it. The shipped two_painters demo shows one model painting an image and another repainting over that actual file.
Two things must both be true. The model must support that output, for example an image capable model. And your tier must allow the file type: Basic exchanges text and source code, Pro adds PDF, and Pro Max and Enterprise allow any type, including images and audio.
The SDK is a C API and a Python package that let your own programs run MCS deliberations. It drives an installed MCS Engine, it does not replace it, so the SDK alone is not enough. It is included with Pro Max and Enterprise, and a $15/mo add on for Basic and Pro. See the pricing page.
We welcome it. Any plan with SDK access lets your own software drive MCS on your machines. If you plan to ship MCS to your customers as part of your product, email sales (at) osinix.com first so we can set up the right agreement.
Single-user MCS runs on one person's computer; MCS Enterprise runs on one server for many people, who sign in from a browser and install nothing. It adds administrators, seats, your company's model keys kept on the server, a choice of which models each person may use, an audit log and a live view of running sessions. The SDK is included. Guide: Release Notes, What each tier gives you.
On your server. Accounts, provider keys and every person's sessions can be read only by the MCS service account, and one person's sessions are kept apart from another's. With cloud models, what people send goes to the provider your administrator chose; MCS Enterprise never contacts Osinix. Guide: Install Guide, Folders and permissions; How MCS keeps people's sessions apart.
A Linux server on x86_64; MCS Enterprise is tested on Ubuntu, Debian and AlmaLinux 9. Minimum: 2 CPU cores and 4 GB of memory. More people, or local models, need more. Guide: Install Guide, Requirements; Choosing a server size.
A seat is an account that can sign in, and disabling an account frees its seat at once. Priced by number of seats, by quote. The licence is a signed file bound to your server and checked on the server itself. Guide: Licensing Guide, sections 3 to 6.
Any combination: cloud models only, local models only, or both in the same session. An administrator adds each provider with your company's key, and the models people may choose; your people never see or enter a key. Guide: Administrator Guide, sections 4 and 5.
Administrators manage people, models and access from a console in the browser, and on the server with the mcs_admin command. Provider keys are entered only on the server, never through a browser. The audit log records sign-ins, sessions and every administrative change, and never records keys. Guide: Administrator Guide, sections 2, 4 and 6.
Yes. People can run sessions from their own scripts with mcs-client or the SDK, in Python or C. A script signs in with an access token that the person makes on their Account page, never with their password. Administrators manage MCS Enterprise on the server with mcs_admin. Guide: Enterprise User Guide, section 8.
Create the service account and run the package's installer with sudo; it then lists the last steps with your own paths. To upgrade, stop MCS and run the new package's installer: it keeps your settings, licence, accounts and sessions. Uninstalling keeps your data unless you add --purge. Guide: Install Guide, sections 1 to 3; Upgrading; Uninstalling.
Email sales (at) osinix.com, or use Request a briefing on the Enterprise page, and tell us how many people will use it. There is no public price or download, and an evaluation licence can be arranged. Guide: Licensing Guide, sections 1 and 4.
Start with the guides: the quick start in your download's docs folder, and the rest in the guides package beside it. They cover installation, usage, licensing, the SDK, and every error code. If the answer is not there, email support (at) osinix.com.
Email support (at) osinix.com. Include your MCS version (mcs --version), your platform, and what happened. Session logs live in each session's logs folder and help a lot.
Yes: hardware vendors, cloud providers, resellers and integrators. Write to partners (at) osinix.com.
That is Claire. She presents Osinix MCS, and she appears in our banners and videos.