Key Features: User Interface as a Service (Vue/Vuetify dynamic rendering from json over REST) Composite Applications from multiple vendors/apps Personal Data Repository & data tokenization Common Communication & Collaboration Components Inter-application workflow & Calendar Centralized Authentication, User Management, Groups/Permissions

1. CloudHaven
The Universal Application Portal
multi-vendor composite applications and collaboration
with personal data control

2. Why?
Too many logins/redundant user & data mgt
Isolated systems don’t work well together
Weak inter-application workflow capability
Isolated collaboration/message systems
Weak personal data control
Complex UI development models
New security threats

3. What?
Vue-based UI Development Platform
Workflow/Composite Application Platform
Common Authentication/User Management
Unified Communication & Collaboration
Consolidated Personal Data Store/Manager
The “user-facing” portion of any application:

4. How (1)?
User Interface-as-a-Service (UIaaS)
Enables:
Dynamically rendered Vue-based UIs
Composite Applications
(fusion of components from multiple vendors/apps)
Embedded context-aware collaboration widgets
Dynamic collaboration content
Personal data control and management

5. How (2)?
Centralized user data storage/control
Enables:
Easy user data maintenance (single copy)
Lifetime centralized access/sharing control
Centralized tracking of access, where-used
Eases data regulatory compliance for apps
Data re-use across applications

6. Philosophy
From tech perspective:
CloudHaven takes the “user entity”
redundantly implemented in thousands of
applications and consolidates that into a
single entity under users’ control.
From users’ perspective:
CloudHaven shifts the focus from the
application to the user – “a user is served
by many applications” instead of “an
application has many users”

7. UIaaS Details
Vue/Vuetify-based component library
Dynamically rendered from JSON provided
by vendor apps via REST
Enables multi-vendor composite apps
user data aware/enabled
Message/calendar/workflow integration

8. “User Layer” around Apps
Web connection
Secure VPN Connection
or Private Line
User Layer
Client Logic
App Logic
Database
Internet
VPN
REST
API

9. High Level Diagram
CloudHaven

10. Life Cycle of CloudHaven App
1. Vendor App registers with CloudHaven
2. User registers with CloudHaven
3. User subscribes to App in CloudHaven “store”
4. User starts subscribed app from “My Apps”
5. CloudHaven sends REST startup request to
App
6. App returns Vuetify-based “page” json
(can include components from multiple
vendors)
7. UIaaS dynamically renders Vue-based json
8. UIaaS makes callbacks to vendor(s)
backend(s) for data, more UI json, CloudHaven
control commands

11. CloudHaven Native Functions
• Conversations/Messaging
• Workflow
• Calendar
• File Sharing/Viewing
• Notifications
• Groups and Permission Management
• Authentication & User Management
• Personal Data Management

12. Development Strategy
Favor adoption over other considerations
(CloudHaven is both radical and ambitious,
thus it is paramount that impediments to
adoption be minimized)
• Develop as open source under the
minimally restrictive MIT license
• Use as the basis for SW Eng/Comp Sci
educational projects so the latest waves of
software developers are familiar with the
model

13. Best for applications …
• Requiring data regulatory compliance
• With high collaboration needs
• With high cross-app integration needs
• Requiring user management, calendar,
file-sharing
• With relatively simple UIs (forms, tables,
tabs)
• Being built from scratch

14. Adoption Strategy
• Develop software as open source/MIT
license
• Open membership with small fee and id
• Equitably owned/democratically governed
by all members
• Provide standalone free services
– Messaging
– Calendar
– Universal Alerts (including from external apps)

15. Business Model
• Member (user)/owner pays nominal fee
• Fee per vendor integration
• Vendor traffic-based fee
• Fee to vendor per user subscription
(or block of users)
• Limited anonymous big data mining
(such as for medical research)
• Sales and service of stand-alone
enterprise versions of the system.

16. Market Sizes
• Total SaaS: $100b
• mHealth Apps market: $40b+
• Digital Health Startups: $14b
• Workflow Management Systems: $1b
• Cloud Enterprise Applications Market: TBD
• Future Enterprise Applications Market:
TBD

17. Business Structure
Multi-stakeholder Platform Cooperative
(Important for vendor neutrality/user advocacy)
Some level of non-voting investment
Cooperative-compatible Preferred Stock
Equity crowd-funded
Can’t be sold to private equity and no
concentration of ownership permitted in perpetuity

18. Competition
Decentralized, self-hosted applications, on-premise
(sandstorm.io, cloudron, anytype.io, nextcloud.io)
Messaging and other user functions
(Google, email/calendar apps, …)
File sharing/data storage
(Google, box, dropbox, truevault)
Collaboration
(yammer, SalesForce chatter, proprietary messaging)
SSO & login managers
(google, facebook, okta, dashlane, ping identity)
Personal Clouds, Other
(polypoly.eu, Percloud (proposal), solid, zerodark)

19. Team
Rich Vann (Founder)
Entrepreneur, SW Developer
Kurt Friedman (Advisor)
Partner, Friedman-Magee Group, SBDC
Advisor
Cal Poly (SLO) 20/21 SW Eng class
25 students currently developing MVP1

20. CloudHaven
The Universal Application Portal
where collaboration, personal data control
and inter-app integration are paramount