SoDelo — a platform for a cooperative ecosystem

Bring people together around shared work

SoDelo connects professional cooperation with practical workflows: offering a service, placing an order, delivering work, accepting the result and participating in joint decisions. The Russian “Со” in the name expresses association and cooperation.

I develop the project with a partner as technical co-founder, covering architecture, engineering direction and implementation while participating in product decisions. Shared ownership needs clear actions and responsibilities behind it.

Where we are heading

SoDelo aims to support a federation of cooperatives in which people can produce, sell, use shared resources and participate in the assets they create. Development, computing services, procurement and a work marketplace should support one another. We are starting in IT, where we have experience and work of our own to build on.

The analytical foundation already includes a concept, economic scenarios, federation design, documents and user journeys. The digital platform helps turn agreements into practical actions. The functions below describe the current application; the federation and shared computing service remain development directions.

A customer could bring a task and find an accountable team. A specialist could offer work, a product or expertise. Someone leading an area of work could assemble people around a testable need. I value a system in which useful work can generate both current income and assets that participants govern together.

Three roles and a common workflow

A specialist presents experience, offers a service and undertakes work. A client chooses help, agrees on the task and accepts delivery. A cooperative participant also deals with membership, documents, voting, financial transparency and exit rules.

These roles may overlap, but a website account does not automatically confer membership. Participation requires its own procedure and agreed terms.

The development version starts with the website: a showcase, project information, an application and a web account. This workflow is available for demonstration; public registration is not open yet. Telegram remains an additional integration channel rather than a prerequisite for entry.

What the working version includes

These are implemented mechanisms whose readiness for an external pilot must be assessed individually.

Area	Application capabilities	Purpose
Expertise	Profiles, portfolios, service showcase, categories, search and favourites	Find relevant help and examine experience
Orders	Creation, responses, performer selection, delivery, revision and acceptance	Preserve the agreement and progress in one place
Membership	Applications, review, statuses, documents and protocols	Separate registration from formal participation
Joint decisions	Votes, choices, participation and results	Make decision processes accessible
Accounting	Balances, transactions, reporting and administration	Track records and the basis for actions
Difficult situations	Dispute cases and exit requests	Provide a process for disagreement and departure
Integrations	Web API, Telegram and experimental external-system access	Connect work with other tools

Delivery is a distinct step: a performer submits work and a client accepts it or requests a revision. Disputes and exit have their own workflows. Cooperation needs rules for difficult days as well as successful ones.

Readiness and limitations

SoDelo is in development. A financial screen does not establish that a bank is connected, real payouts operate or legal preparation is complete.

Bank operations and some electronic-signature mechanisms still use test implementations. External message delivery, financial integrations and operational readiness need separate validation. The API direction is also experimental rather than a production integration platform for third parties.

The current offer is a demonstration and a bounded pilot with agreed participants, terms and acceptance criteria. I will publish launch and joining information separately when those arrangements are ready.

Technical foundation

The web application uses Next.js 16, React 19 and TypeScript. The backend uses Scala 2.13, ZIO 2, ZIO HTTP and Tapir, with PostgreSQL, Flyway migrations and Redis. Web authentication and Telegram integration support distinct entry paths.

The substantial evolution is the independent web product and its connected workflows. My engineering focus is consistency between user actions, API behavior, permissions and stored state throughout work and participation.

Registration is coming

We are preparing the cooperative’s website and participation terms. Public registration is not open yet. Follow my Telegram channel: I will share the registration link and joining instructions there when they are ready.

What we can explore together

A demonstration can follow the showcase-to-order workflow, delivery and revision, then examine membership applications, documents and decisions separately. For a pilot, I suggest one real task with explicit roles and an agreed definition of success.

I welcome discussions about development, computing, sales, procurement and organising the work. You can bring a concrete task, experience or a resource. The first conversation requires no contribution payment. Each pilot needs an agreed outcome, workload and budget before it begins.

Discuss SoDelo and a shared project →