// What you get

Sessions now, credits at launch.

Two things are on the table. One is worth something today; the other is worth something the day the platform ships. Both are aimed at the same person - someone building a system that is hard enough to be worth designing properly.

Credits and discounts at launch

Core, Genesis and Prism are Apache 2.0 and free to run locally - that does not change. Cosmonapse Cloud is the part that will eventually be paid. Everyone who joins the programme is recorded now and gets launch credits plus a standing discount when Cloud goes live.

Architecture sessions with the team

Live working sessions on your system, not a sales call. We whiteboard the thing you are actually building: where the boundaries go, which parts should be Neurons, what belongs in memory, where a human has to sit in the loop. Subject to availability.

A direct line to the roadmap

0.2.0 is being shaped right now. Rough edges you hit go on the list with your name against them, and you hear back about what happened. Early access is the shortest path from a real workload to a protocol change.

What we ask in return

Nothing that costs money and nothing that ties your hands. Build something you actually need. When it breaks - and at 0.1.x it will - tell us exactly where, with enough detail that it can be reproduced. That is the whole arrangement. There is no NDA, no exclusivity clause and no requirement to say nice things in public; a blunt write-up of what did not work is more useful to us than a testimonial.

How it works
01

Apply through the form

Two minutes. What you are building, the stack you are on, and how far along you are. There is no bar to clear on company size or funding - a solo project with a real problem behind it is exactly the profile.

02

We read it and reply

Every application gets a response, including the ones we cannot take. If it is a fit, we come back with times for a first session.

03

We architect it together

Remote, roughly an hour, screen and a diagram. We go through the system end to end and leave you with a design you could build on Monday. Framework-agnostic: if Cosmonapse is the wrong tool for what you are doing, we will say so and help you pick the right shape anyway.

04

Credits land when the platform does

Your slot and join date are on record from the day you are accepted. When Cosmonapse Cloud launches, the credits and the discount are applied to your account - no re-application, no window to miss.

// Fit

Who this is for.

The programme is small on purpose, so it is worth being honest about who gets value from it and who would be better off waiting for 0.2.0.

A good fit if

  • You have a real system in mind - a product, an internal tool, a research setup - not a tutorial to follow
  • Multiple models, tools or services have to coordinate, and a single prompt-and-response is clearly not enough
  • You are comfortable on alpha software and can work around a rough edge instead of being stopped by it
  • You are willing to say what broke, in enough detail that it can be fixed

Probably not yet if

  • You need a production SLA today - Core is 0.1.11-alpha and the protocol is not frozen until 0.2.0
  • You are looking for a managed hosted service right now - Cloud is a 1.0.0 target, not a thing you can buy
  • You want an agent that is one model behind a chat box - you do not need a protocol for that
  • You cannot share anything at all about what you are building, which makes an architecture session hard to run
Questions worth answering up front
?

Does it cost anything?

No. The programme is free, the sessions are free, and everything you would build on today is open source under Apache 2.0. The credits exist because early members will have spent time on a product that was not finished yet.

?

How firm are the credits?

It is a commitment we are putting in writing on a public page, not a signed contract - and we will not attach a date to it, because 1.0.0 and Cloud do not have one. What is fixed is the order: everyone who joins during early access is in before anyone who signs up on launch day.

?

Do I have to build on Cosmonapse?

No. The sessions are about your architecture. Plenty of systems are better served by something else, and we would rather be useful than convert you. If Cosmonapse does end up being the right fit, that is a better outcome for both of us than talking you into it.

?

Who owns what I build?

You do. No NDA, no exclusivity, no claim on your code. You are free to talk publicly about the sessions, the product and where it fell short.

?

How many slots are there?

Enough that the sessions stay real. Sessions are run by the people writing the code, so intake is limited by how many hours exist in a week - which is why the form asks what you are building rather than just for an email.

?

What happens to my form response?

It goes to a Google Form and is read by the team. We do not need your source code or credentials to run a session, and we do not ask for them.

Tell us what you are building.

The form takes about two minutes. If you would rather look before you leap, the quickstart runs a two-node system on your machine in a few commands, and the roadmap lays out exactly what is shipped and what is not.

Slots are limited and sessions are subject to availability. Prefer email? dev@cosmonapse.com