CloudWinks · The framework

How the CloudWinks framework worksFor business and technology leaders

CloudWinks is one framework underneath every app. The shared parts are built once, and each app adds only what makes it different. Here is how that works, in plain terms.

See all application briefs · PDF

1. Built from definitions, not from code

Every CloudWinks app is described in definitions: its tables, screens, fields and menus. One pipeline builds the database from those definitions, with a separate, clean area for each app, and one shared service layer serves the data. A single Flutter client runs every app, on the web, on Android and on the other platforms Flutter supports: Windows, iOS, macOS and Linux.

For a business, this means a new app is a set of definitions rather than a new software project, and an improvement to a shared part reaches every app that uses it at once.

2. Base functions: the same management steps on every item

Every item a CloudWinks app manages, whether a horse, a project, a property or a purchase order, gets the same set of management steps:

Goals and measures, dependencies (PERT and Gantt), communication and history, approvals, location (Roady) and documents and compliance follow the same pattern.

Base functions never copy data or features. Each one is a doorway from the item to the controls that already live in the app that owns them, such as MediaMogul, TaskMaster, TimeTracker, BeanCounter, Roady and BullChat. Every item carries its own type, so any app can open it directly.

3. Owned by a person or a company, shared where it makes sense

Every record belongs to someone. Where money or security is involved, the record belongs to the person or company and uses their own KeyKook account, and other people and companies cannot see it. Where no account is needed, people and companies share ready-made CloudWinks templates, so nobody has to set the same thing up twice.

4. One way to connect outside services: CosmosCall and KeyKook

CosmosCall is the integration hub: a single register of outside providers, webhooks and mappings. Every connection to an outside service, such as Google, is a KeyKook connected account that belongs to a person or a company. CosmosCall points to that account, and passwords, keys and other secrets live only in KeyKook. A calendar read from Google, for example, arrives through CosmosCall into the shared calendar that every app can use.

5. BusyBody: one window over everything

BusyBody subscribes to other apps and sources, such as TaskMaster, Google Calendar and Microsoft To Do, and combines their items in calendar, Gantt, list and other views. Each item opens in the app that owns it. BusyBody brings a person’s work together in one place without replacing the apps that do the work.

6. Runs on the server or on the device

Every app that needs heavier processing can run that work either on the server or on the user’s own device, on every platform Flutter supports: Windows, iOS, Android, web, macOS and Linux. Work is spread across user devices as much as possible, so servers are not overloaded. Money, security and company-account work always stays on the server.

7. One app for each job

Each job has one home. FireSticks covers shooting sports from a personal inventory to a full club and range, with ShootingClubs as part of it, in the Hobbies and sports group. MiSalud, the central health record in the Home, family and everyday life group, includes the personal medicine tracker for doses, refills, prior authorisations and cold-chain medicines, while Pharmakologie runs pharmacy operations. YumYum covers food from farm to table, with TraceWinks farm-to-restaurant tracking built in. StableKidz sits with the agriculture and equine apps, alongside HuntingLodge.

See all application briefs → · How it works →