CloudWinks · Foundation apps

CloudWinksTechnical brief

CloudWinks is the shared home for a family of business apps. It describes screens, menus and common behavior in reusable definitions, giving organizations a consistent experience and reducing repeated development work.

Read the business brief · PDF

1. Architecture in brief

Application definitions flow through Python Build/Import/Seed into PostgreSQL metadata and application schemas. The C# GenericExecute API provides the execution boundary; Flutter renders the shared experience. Registry, control, field and menu definitions describe the common interface rather than requiring a separate handcrafted screen for every form.

2. Service boundary and intake

The application catalogue identifies apps and their schemas. Control and field metadata define screens, dependencies and menu choices. Navigation services save and restore a user’s place with company-access checks and bounded history. Password authentication supplies the platform access token used by subsequent protected API requests.

3. Data handled

CloudWinks holds app registrations, schema references, controls, fields, menus, app-user/app-company context and saved navigation position. Crux owns shared identities, KeyKook owns access and credentials, and specialist apps own their business data. Keeping these responsibilities separate supports consistent reuse.

4. Integrations and ownership

The Flutter shell hosts app capabilities through common framework services and interfaces. Crux and KeyKook anchor identity and access; other apps contribute specialist functions without making the framework responsible for their business rules. Definition-driven configuration supports different application selections and starting screens for different businesses.

5. Security and access

API authorization and company access are enforced at the service boundary; visibility of a menu is not the security boundary. The client uses platform bearer tokens for protected calls and clears them on logout or relevant authorization failures. Customer-specific data access, identity-provider handoff and shared navigation form one security-sensitive customer journey.

Competitive context

AlternativeIts focusCloudWinks product focus
AppsmithCustom apps built with connected data and reusable screen components.A shared definitions-led model across a family of business apps.
RetoolData-connected apps built with components and code.Common identity, navigation and business-app services in one framework.

Read the business brief →

← More Foundation apps apps · All application briefs · How the framework works