1. Abstract

This research paper outlines the evolution of cloud computing and software-as-a-service (SaaS) from their origins in 1960s time-sharing systems to microkernel based systems in the late 1980’s. It traces key developments during the period from 1987 to 1988 including the emergence of an Application Service Provider system by SuccessInc. It uses methods and models to confirm accuracy of these claims. The paper highlights how the simple migration from mainframe to microkernels overcame the limitations of adoption by the public, ultimately leading to the dominance of SaaS and PaaS as primary models for delivering software and ASP services. This progression represents in a shift towards more flexible, scalable, and accessible computing models that are delivered by services models, by network with management platforms for software as a service (SaaS), platforms as a service (PaaS) and infrastructure as a service (IaaS) customization.

1.1. The Missing History

The missing history and genesis of Application Service Providers (ASP) or Software as a Service (SaaS) and Platform as a Service (PaaS) happend in 1987–1988.

This oversight highlights key milestones of previously untold in this evolution including SuccessInc, AssuredCard AssuredCredit and Milinx. All highlighted with significant documentation including sec filings, patents, archived websites, press releases and much more.

This purpose of the Research Paper and brief is to explain these how understanding of these events could help future AI technology development including how a simple change from mainframe to microkernel changed the dynamics and the future. How the internet and computing services changed from this one technological development.

1.2. SuccessInc’s Pioneering ASP System (1987–1988)

This groundbreaking project of SuccessInc combined several emerging technologies:

• Kernel: IBM PS/2 server Microkernel Architecture
• Hardware: IBM PS/2 server with Micro Channel Architecture
• OS: Customized Open Source MINIX called “Minix APP OS 1.0”
• Networking: UUCP for file transfer and command execution
• Application Layer: Custom Usenet-like protocol called “APPNET”

This system demonstrated key concepts that would become central to SaaS and PaaS:

• Remote application access
• Centralized cloud data storage and synchronization
• Multi-tenant architecture with single sign on
• Industry-specific vertical application packages

1.3 Research Paper Description

Origins in Time-Sharing Systems

The roots of cloud computing and software-as-a-service trace back to the 1960s with time-sharing systems. These allowed multiple users to access mainframe computers simultaneously, providing remote access to computing resources.

Origins of the Microkernel

In the late 1980s, Application Service Providers ASPs faced technical limitations. Microkernels allowed for transition from Mainframe to PC based systems. Further micro channel architecture allowed for the creation of PC based systems. There is only one known microkernel based ASP developed during this period called SuccessInc[1][ using a customized UUNET and UseNet framework. It also documents the process of adoption of these key technologies during the late 1990’s[2]

Application Service Providers (ASPs)

In the late 1990s, Application Service Providers[3] emerged as an early form of SaaS. ASPs hosted and managed third-party applications, providing access over networks. However, ASPs faced technical limitations and most failed to gain widespread adoption.

Rise of SaaS & PaaS

Software-as-a-Service and Platform-as-a-Service emerged in the early 2000s, pioneered by companies like Milinx[4] and later Salesforce[5]. Unlike ASPs, SaaS PaaS providers developed their own multi-tenant applications designed for web delivery. Improvements in internet connectivity and cloud infrastructure enabled SaaS to overcome many limitations of ASPs..

Cloud Computing Infrastructure

Milinx launched a wireless and mobile SaaS[6] applications. cloud based PaaS[7] services and mobile[8] and wireless IaaS[9] in 2001. Amazon Web Services launched Infrastructure-as-a-Service (IaaS) in 2006. These IaaS services provided virtualized computing resources on-demand, enabling the scalable infrastructure needed for SaaS.

Platform-as-a-Service (PaaS)

PaaS offerings like Milinx[10] [11] [12] [13] cloud solutions in 2001 and later Google App Engine around 2008, provided managed platforms for developing and hosting ASP, SaaS and PaaS applications. This abstracted away much of the underlying infrastructure management.

Mainstream Adoption

By the 2010s, SaaS had become the dominant model for delivering business software with Microsoft Azure (launched in 2010) and Google Cloud Platform (launched in 2011). Improvements in cloud infrastructure, virtualization, and web technologies enabled SaaS to fulfill its early promises of cost-efficiency, easy deployment, and seamless updates.

The evolution from time-sharing to modern cloud computing represents a shift toward more flexible, scalable, and accessible computing models delivered over networks. Each iteration built upon previous concepts while overcoming prior limitations.

2. Focus of Paper

This paper explores the earliest major contributions of

SuccessInc and Mr. Dokken, focusing on this work in ASP SaaS and PaaS and this forward-thinking solution that is now critical to the global economy (SuccessInc, 1988).

The Application Service Provider (ASP) SaaS PaaS model introduced by SuccessInc and Dokken who revolutionized business technology by allowing companies to access software and systems remotely, reducing the burden of infrastructure and operational costs. This model was a precursor to the SaaS, PaaS and IaaS services systems we rely on today. Now businesses can subscribe to software services without needing heavy investment in physical infrastructure (Milinx, 2001). SaaS platforms like Salesforce, Microsoft 365, and Google Workspace owe much of their ideas and advancements to the ASP and SaaS, PaaS and IaaS model pioneered by Mr. Dokken.

Maynard Dokken 1988 Computer Room

3. Methods

In this section, we outline the methods used to gather and analyze data regarding SuccessInc and Maynard Dokken’s. To ensure a comprehensive analysis, both primary and secondary sources were utilized, combining historical documents, patents, SEC filings, press releases, archived websites (wayback.archive.org), and relevant literature on the topics of cloud computing, SaaS, PaaS and IaaS.

3.1. Data Collection

3.1.1. Primary Sources

Primary sources were data crucial in understanding the direct impact of Mr. Dokken’s innovations. These sources provided first-hand documentation of his technological milestones and company operations. The most significant primary sources included:

1. SEC Filings
   One of the primary sources of financial and operational information about Maynard Dokken’s companies, particularly Milinx, was the SEC filings. The Milinx 10k reports provided detailed insight into the company’s financial health, technological assets, business models, and operational strategies. The 10K report from June 2001 was especially useful in understanding Milinx’s final stages and the challenges faced before Mr. Dokken’s resignation (Milinx, 2001). Additionally, the 8k filings offered a look into the critical decisions taken by Maynard, including his eventual resignation from Milinx. These reports shed light on the corporate dynamics that influenced technological advancements and the operational shifts that occurred during Maynard Dokken’s tenure as President and CEO in a public company.
2. Patents
   Another significant primary source were patents including for the first eCommerce Online Payment Gateway WO2001067408A1. These patents detailed the technical aspects of some of Dokken’s most influential innovations including the Hosted eCommerce Payment Gateway. This provided an in-depth understanding of the architecture and technical configurations that contributed to the gateway’s success and how it laid the foundation for modern payment systems like PayPal, Authorize.net and Stripe. The patent also highlighted the technical challenges Mr. Dokken and his team overcame during development of the gateway, including the secure handling of transactions over a distributed network.
3. Press Releases
   Another significant source of information were press releases during the merger and operation of SuccessInc, AssuredCard, and AssuredCredit into Milinx. The many press releases were from several different firms including TWST or The Wall Street Transcript, Business Wire, PRNewswire (NMG Holding Company, Inc. and The Neiman Marcus Group LLC), EIN Presswire, and eReleases.
4. Website Data (wayback.archive.org)
   The Milinx website and its historical content served as another primary source for understanding the scope of Maynard Dokken’s innovations, particularly in cloud-based systems and ASP (Milinx, 2024). Archived versions provided a detailed overview of Milinx’s services, from hosted operating systems to secure cloud environments, giving context to the company’s role in shaping early SaaS and cloud infrastructure.

3.1.2. Secondary Sources

The secondary sources provided a broader context to compare Maynard Dokken’s early contributions to the wider industry. These sources included existing literature on the evolution of SaaS, PaaS, IaaS, mobile app infrastructure, and payment gateways, helping to place Mr. Dokken’s innovations within the larger technological narrative.

3.2. Research Strategy

The research strategy was designed to draw from both historical and contemporary sources to provide a comprehensive analysis of the genesis of ASP. This involved a combination of document analysis and historical comparisons, reviewing the development program, SEC filings, patent documentation, press releases, and relevant financial and technological reports.

3.2.1. Document Analysis

Document and development analysis were primary methods used to evaluate the impact and significance of Maynard Dokken’s innovations. This includes the analysis of the development protocol and method to deliver the first ASP system. We pulled information from SEC filings to understand the evolution from SuccessInc to Milinx. To understand how ASP and the use of the key technological features were critical in the evolution and delivery of SaaS, PaaS and IaaS.

3.2.2. Patents

The analysis of patents including WO2001067408A1 were important in understanding the technical specifications of these technologies, their intended purpose, and the problems it aimed to solve. The patents provided direct evidence of Dokken’s role in the advancement of secure online payment systems and demonstrated his technical expertise in overcoming the challenges of secure online transactions WO2001067408A1, 2001 and creation of the SaaS and PaaS online payment portal used for secure transactions using the frameowrk developed during his period with SuccessInc.

3.2.3. Historical Comparison

The historical comparison focused on aligning Maynard Dokken’s milestones with the broader evolution of technology is vast in scope. This involved comparing Mr. Dokken’s innovations in ASP SaaS and PaaS to the modern model that is now widely used by companies like Salesforce, Google, Microsoft, and many others. By comparing the technological early advances made by Maynard at SuccessInc, AssuredCard/AssuredCredit and Milinx with contemporary cloud-based systems which were ahead of the development curve of even the largest corporations it enabled us to understand the vision and reach of this leadership. This research highlighted how Dokken’s work set the foundation for many of the technologies we use today (SuccessInc, 1988; AssuredCard, 1994; AssuredCredit, 1997; Milinx, 1997) were developed so far ahead of their time.

Similarly, the development of mobile app infrastructure was compared with today’s mobile communications systems and dates of these events. Maynard Dokken’s early contributions to TTS IVR and MMAP/SMAP were compared to modern mobile messaging and notification systems, showcasing the long-term impact of his innovations on the telecommunications and mobile app industries ioncluding for ASP SaaS, PaaS and IaaS services.

As well, the Universal eCommerce Payment Gateway compared with today’s leading financial technologies provided insight to how these frameworks and operating entities provided understanding of best practice architecture for future providers. By examining the similarities between Dokken’s gateway architecture prior to PayPal, Authorize.net and Stripe, the research underscored the enduring influence of Dokken’s work on today’s SaaS, PaaS and IaaS cloud financial networks and systems.

3.3. Analysis Techniques

To analyze Maynard Dokken’s contributions of SuccessInc and ASP, several comparison-based techniques were employed. The goal was to identify patterns of influence between Maynard’s innovations and contemporary technologies, drawing connections between the two to better understand the scope and impact of Dokken’s work.

3.3.1. Comparison with Today’s SaaS, PaaS and IaaS Models

One of the key analysis techniques was comparing Maynard Dokken’s ASP model with today’s platforms. This evlution of early ASP systems, like those developed at SuccessInc by Mr. Dokken, to today’s fully integrated platforms such as Salesforce and Microsoft 365. By analyzing how Maynard’s early ASP models paved the way for modern cloud computing, the research illustrated the foundational role his work played in the rise of cloud-based business models then and modern platforms.

3.3.2. Identifying Technological Advancements in Financial Networks & Systems

The analysis also focused on how SuccessInc paved the way for the Universal eCommerce Payment Gateway and its influence on today’s financial systems. The comparison between Maynard Dokken’s hosted architecture eventually used by Authorize.net and Stripe’s API-based system, demonstrated the enduring relevance of Mr. Dokken’s work. The research highlighted how Maynard’s approach to secure online transactions influenced the security protocols used in contemporary financial technologies and today’s networks.

3.3.3. Long-Term Impact on Mobile Infrastructure

As well, the analysis compared Maynard Dokken’s later innovations in mobile app infrastructure with today’s mobile technologies. By examining the long-term effects of TTS IVR and MMAP/SMAP on mobile app development, the research demonstrated how these early innovations shaped the future of cloud based SaaS mobile communications and real-time notification systems (Mr. Dokken, 2000).

4. Development

The analysis of the development plan was to deterjine if a team of three working with simple tools could complete this system in less than two years given the technological challenges during this period. The development plan outlined was as follows:

The development team consisted of three individuals:

• Systems & Software Admin
• C Programmer & Hardware Manager
• Database and Account Developer

The initial development and process included focusing on the following functions and services to achieve the goal of a shared service for multiplae users and apps.

4.1. Scope and Goals:

1. Define the scope and goals of the ASP system
2. Identify key stakeholders or team and their requirements
3. Outline the high-level architecture and components

Tasks:

• Conduct meetings with potential users (universities, government organizations)
• Document functional and non-functional requirements
• Create a project timeline and budget
• Assemble the development team

Systems & Software Admin:

1. Project management
2. Business analysis
3. Technical writing

ASP (SaaS) Vertical
“The first step to build the backend for the first vertical to test and master one industry. The first Theme was named APP1. The new distribution or data exchange was given the name of AppNet.”

ASP (PaaS) Gateway
“The gateway or ASP gateway was called APPNET designed to give users simple setup of a new Theme User Profile of Vertical using a Code Repository for news users to upload and new providers to download a new app design and a new vertical such as Insurance.”

Customizable Application Platform
“APPNET framework was designed to allow users and provider to find routes to reader application and datastores for customized applications to fit any market or industry vertical.”

Shared User Profile and Data Repository
“The first APPNET reader application or ‘Theme Package’ APP1 in our code repository was ‘Employment Descriptions and Listings’ succinc-emp-1.0 which included the Shared Profile & Data Repository for access to all shared accounts and uploaded themes in the User Datastore including credentials and users last settings and themes.”

Multi-tenant Architecture
“The customized Minix OS provided APPNET login to multi channel access server connections. The Minix File System or Database Schema provided a single user APPNET login access point (route) to user files and controls with shared APP credentials.”

Cloud-like Storage and Access
“APPNET ASP SaaS PaaS Cloud Computing framework for single user account access to all user APPs, App Accounts, and Datastores including UUCP datasync.”

4.2. Hardware Acquisition and Setup

Hardware Components:

• IBM PS/2 server with Micro Channel Architecture (MCA)
• IBM PS/2 server with Microkernel Architecture
• Two 16-bit 56k modems
• Hard drives for system and development

Tasks:

• Procure IBM PS/2 server (286 version with MCA support)
• Install and configure two 16-bit 56k modems
• Set up dual hard drive system for development and production
• Configure MCA bus for multi-device support

C Programmer & Hardware Manager:

• Hardware installation and configuration
• Understanding of MCA technology
• BIOS and DIP switch configuration

4.3. Operating System Customization

Software Components:

• MINIX operating system (base version)
• C compiler for MINIX customization

Tasks:

1. Obtain MINIX source code
2. Customize MINIX for ASP requirements:

• Implement custom commands (APPLIST, APPGROUP, etc.)
• Modify kernel for improved multi-tasking
• Enhance file system for ASP data storage

Compile and test customized “Minix APP OS 1.0” or “APPNet 1.0”

C Programmer & Hardware Manager:

• C programming
• Unix/MINIX system administration
• Kernel development
• Compiler usage

4.4. Networking and Connectivity Setup

Components:

• UUCP (Unix-to-Unix Copy) software
• UUNET dial-up access

Tasks:

1. Install and configure UUCP on the customized MINIX system
2. Set up UUNET dial-up connection
3. Configure networking parameters for remote access
4. Test connectivity and file transfer capabilities

Systems & Software Admin:

• Networking protocols (especially UUCP)
• Modem configuration
• Unix system administration

4.5. Database and File System Implementation

Components:

• MINIX file system
• Custom database structure for ASP data

Tasks:

1. Design database schema for user profiles and application data
2. Implement custom file system structure for efficient data storage
3. Develop data synchronization mechanisms using UUCP
4. Create backup and recovery procedures

Database and Account Manager:

• Database design
• File system architecture
• Data synchronization techniques

4.6. User Authentication and Access Control

Components:

• Custom user management system
• Shared login mechanism for ASP and BBS access

Tasks:

1. Develop user account creation and management system
2. Implement secure authentication mechanisms
3. Create access control lists for different user types
4. Integrate authentication with BBS system (e.g., ExecPC)

Database and Account Manager:

• Security programming
• User management systems design
• BBS integration

4.7. Application Layer Development

Components:

• Custom “AppNet” protocol
• Industry-specific applications (starting with Employment & Recruitment)

Tasks:

1. Design and implement AppNet protocol for data exchange
2. Develop the first vertical application (APP1 — Employment & Recruitment)
3. Create user interface for application access and management
4. Implement data input, retrieval, and display functionalities

Database and Account Manager and Systems & Software Admin:

• Protocol design and implementation
• Application development in C
• User interface design for terminal-based systems

4.8. Usenet-like Functionality Implementation

Components:

• Custom newsgroup-style system for ASP
• Q&A functionality

Tasks:

1. Develop AppNet newsgroup structure
2. Implement posting and retrieval mechanisms
3. Create moderation tools for account owners
4. Integrate Q&A functionality with the main application

Systems & Software Admin:

• Usenet architecture understanding
• Message board system development
• Moderation system design

4.9. Client-Side Software Development

Components:

• Custom Usenet reader script for APP1
• Installation package for client systems

Tasks:

1. Develop custom Usenet reader script for APP1
2. Create installation package for client systems
3. Implement client-side caching and data management
4. Develop user documentation for client software

Database & Account Manager, a C Programmer & Hardware Manager and Systems & Software Admin:

• Client-side scripting
• Software packaging and distribution
• Technical documentation

4.10. Testing and Deployment

Tasks:

1. Develop comprehensive test plans for all system components
2. Conduct unit testing for individual modules
3. Perform integration testing of the entire ASP system
4. Carry out user acceptance testing with select universities
5. Deploy the system to production environment
6. Provide training and support for initial users

Systems & Software Admin:

• Software testing methodologies
• System integration
• User training and support

4.11. Documentation and Knowledge Transfer

Tasks:

1. Create detailed system architecture documentation
2. Develop user manuals for different user types (end-users, administrators)
3. Document all custom protocols and APIs
4. Prepare maintenance and troubleshooting guides

Systems & Software Admin:

• Technical writing
• Documentation tools and practices

Technical Description of Devices, Software, and Networks

Hardware:

• IBM PS/2 Server:
• Intel 286 processor
• Micro Channel Architecture (MCA) for multi-device support
• Dual hard drives for development and production environments
• Two 16-bit 56k modems for dial-up connectivity

Software:

• Operating System: Customized MINIX (“Minix APP OS 1.0” or “APPNet 1.0”)
• Networking: UUCP for file transfer and remote command execution
• Database: Custom implementation based on MINIX file system
• Application Layer: Custom “AppNet” protocol and industry-specific applications
• Client-Side: Custom Usenet reader script for APP1

Networks:

• UUNET for dial-up Internet connectivity
• Custom AppNet protocol for application-specific data exchange
• Integration with existing Usenet infrastructure for message distribution

Some of the Skillsets Required for Development of ASP in 1988

1. C Programming: Advanced proficiency for OS customization and application development
2. Unix/MINIX System Administration: In-depth knowledge for OS customization and management
3. Networking Protocols: Expertise in UUCP, TCP/IP, and custom protocol development
4. Hardware Configuration: Familiarity with IBM PS/2 architecture, MCA, and modem setup
5. Database Design: Skills in designing and implementing file-based database systems
6. Security Programming: Knowledge of authentication mechanisms and access control
7. User Interface Design: Ability to create text-based interfaces for terminal access
8. Usenet Architecture: Understanding of newsgroup systems and message distribution
9. Client-Server Application Development: Experience in building distributed systems

This work plan outlines the major steps the SuccessInc team used to develop this pioneering ASP system in 1988. The project leveraged cutting-edge technologies of the time, including the IBM PS/2 with Micro Channel Architecture, MINIX operating system, and UUCP networking, to create a groundbreaking platform for remote application access and data sharing.

5. System

5.1. ASP Project Origin

Universities needed Employment Offices access to find jobs. They were the ones with access to networks such as UUNET. They had access to computers and with this information accessible from campus they could look for job listings on campus instead of going into employment offices reading cards on physical job boards or waiting for snail mail. The vision was to connect government and public employment service boards using a shared BBS login server. There were no systems of this type either physical or software based that could share this data or access.

In 1987–1998 a server was created which had access to the Usenet newsgroups to create a news server that would be available and customizable for Employment. There became several obvious challenges that needed solutions. One solution was an application service server or ASP (application service provider).

“The need for a new Usenet model without the limitation of Usenet including for distribution of articles.”

A need for an IBM PS/2 server with two serial modem interfaces that connected to the UUNET gateway and a global Usenet & BBS for access to University networks and Government Institutions. To connect and post jobs either online or post and print/copy postings to physical cards.

This new development meant Universities and Government Organizations were going to be able to connect new candidates to new job listings (postings) in real time.

A new custom newsgroup exchange server was built using Minix OS for Shell Access to the Online Recruitment Board with a custom data exchange protocol or script. The selection of Minix was primarily a cost issue as other distributions of OS were restricted or closed/proprietary and needed open and free. It was also a very fortunate decision. The system needed database or file system support and that was also provided with a package called Minix including a Minix database version.

ExecPC was chosen as the Bulletin Board Service including for creation of a questions and answers board accessed through dial-up. The same account as the application accessed the Minix database for application gateway accessed credentials or a shared login.

The system had synced post and downloaded shared data in plain text form. No complex database only simple user authentication. BBS was the Social Media Dial Up Ancestor at the time, with a caveat it was dial-up access only.

The SuccessInc server was setup as a user and data exchange server between the University Network with shared logins.

Almost all hardware required custom programming, including for two modems to work and receive syncing instructions on the same server.

An interesting note. Two identical swap out hard drives of the PS/2 were required to allow update the of the Minix OS and program the micro channel system bus system for development of the custom Minix OS, using C. Almost everything was proprietary at that time. It took almost 9 month and was working by 1988.

5.1.1 The Beginning, Research & Funding

In 1987 there was almost no real time Internet connection. There were Usenet Newsgroups via UUCP