Skip to Content

Questions and answers

About the MyAIde platform: how the suites are built, what they cost, and where your data lives.

This page covers the platform only. Questions about clubs, events and the blog are answered in those sections.

Your data belongs to you

Your customer base, documents and operation history do not depend on anyone else's goodwill or access. You can export everything and move it wherever you want, at any time.

Export without asking us

Any list goes to CSV or XLSX straight from the interface. A full database copy with attachments is taken with standard tools.

The system runs without us

Deploy your copy on your own server, or hand it to any other contractor.

Open licence

Odoo 18 Community Edition and modules under LGPL-3. No keys, no activation, no lock-in.

About the platform

A set of ready-made working suites on Odoo 18 Community Edition: club, event portal, industry registry, academy, projects, HR, access control, manufacturing, landscape, startup studio, buyer's toolkit. Each suite is a working system, not a demo.

A complete area of work with its own models, permissions, reports and training for every role. A suite is switched on in days rather than built over six months, and works right away.

No. Suites are taken one at a time and fit together: shared reference data, one set of roles and permissions, one academy.

You do not start from a blank slate. Models, permissions, reports and a course per role already exist — what remains is tuning them to your processes.

Odoo 18 Community Edition, Python 3.12, an OWL 2 interface. Modules are licensed under LGPL-3.

Russian, English and Spanish.

Cost and rollout

The suites themselves are free. You pay only for customisation to your own needs.

Customisation to your processes: new fields and reports, integrations, non-standard logic. Plus installation and configuration if the system goes on your own server.

Your choice: our hosting or your own server.

No. On your server, installation and configuration are paid. On our hosting we deploy it ourselves.

A suite is switched on in days. Customisation time depends on scope — we estimate it before starting, not afterwards.

Data and portability

You do. The customer base, documents and operation history are yours, and access to them does not depend on anyone else's decision.

At any time, without asking us. Lists export to CSV and XLSX straight from the interface; a full database copy with attachments is taken with standard tools.

You take the database copy and the files and deploy the system yourselves or with another contractor. Modules are LGPL-3 — no keys, no activation, no buying your access back.

No. Every organisation has its own database.

Portal account

A portal account: clubs and communities, event registration, academy courses, your own requests and proposals.

No, these are separate things. The account is about taking part in the portal. A suite is a system for your organisation and is deployed separately.

No.

Write through "My requests" — it is open to any user, no special permissions needed. The same place lets you propose a new community or event.

Did not find your answer?

Ask directly — we answer specifics rather than in generalities.