CloudWinks
CloudWinks is the shared home for the applications, their menus and common screen elements. It keeps the application list and helps people move between apps.
CloudWinks · Application briefs
Shared services and the common tools other apps build on.
Foundation is the shared-service layer every CloudWinks app builds on: identity, sign-in, files, communications, integrations, scheduling, tasks and time.
CloudWinks is the shared home for the applications, their menus and common screen elements. It keeps the application list and helps people move between apps.
Foundational identity: users, companies and icons.
Authentication and access: credentials, sessions, roles, multi-factor sign-in, and the registration and verification flow.
Central error logging, grouping and audit.
Files and media: storage, classification, sharing and document metadata — one place for every application’s uploads.
The integration hub: outside providers, webhooks and mappings, connected through each person’s or company’s own KeyKook account. Secrets stay in KeyKook.
Unified communications — email, SMS and push — with providers, routing rules and an outbound queue.
A person’s unified window: it combines items from TaskMaster, Google Calendar, Microsoft To Do and other apps in calendar, Gantt and list views, and each item opens in the app that owns it.
Maps and geospatial work: routes, pins, polygons and geofences — the layer behind field work and location tracking.
TheIntegrator defines how information from one system is changed into the format another system needs. It carries outside connections such as the QuickBooks load, bank feeds, payment-provider calls and tax e-filing.
Business process management: process definitions, steps, and running instances — approvals and multi-stage work as data.
The central scheduler: it decides when a window has arrived, hands the work to the owning application once, and records the handoff.
External parties, roles, contact points and outreach status — a shared address book. Rolodex does not send messages.
AI agent orchestration: agents, nodes, flows and tests. The framework for work that runs without a screen in front of it.
Regulatory compliance and governance monitoring, applied per application where a sector needs it.
A business rules engine: rule definitions, rule sets, executions and decisions — kept in one place so products behave consistently.
Report templates, schedules, executions and an audit trail. Applications produce real documents without each handwriting them.
Implementation planning: modules, gaps, phases, tasks and prompts. The framework’s own method, modelled as an application.
Database migration and schema introspection — how an existing system’s structure becomes definitions the platform can build.
A showcase of the field types the framework can render — useful as a reference for anyone specifying a new screen.
Conversation inside an application, using the same identity as everything else. Messages stay tied to the item they are about.
Caching, endpoint health and failover — the scaling layer that keeps the platform fast and spreads work across servers.
Task management: tasks, work orders, projects and checklists in one shared place for personal and company work.
Time tracking: who worked, when and on what, with attendance records and timesheets.