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 and Email at some Universities. These were terminal dial up sources of information including bulletin boards. You could get technical information, programs and scripts using Bulletin Board Services (“BBS”) through networks including UUNET although most were outdated. As well you could get technical information from your local computer shop or shops for IBM & NCR. Book stores sometimes had, at the very back or on a second floor, random technology material or you ordered from a printed catalog at the cash desk. Very time consuming. Startup or entrepreneurial funding for this kind of development was non existent. Self funding and teaching the only solution at that time.

Universities did not have advanced courses and most engineers at IBM and Xilinx were not focused on customizable OS or open script based application platforms much less open source Unix or customizing Usenet. Regardless without technology advancements no matter how minor this platform would not have been possible. Without the work of Andrew Tanenbaum the creator of Minix Unix and File System there would not have been open source code for customization needed.

Tanenbaum was changing the architecture of what is now a microkernel based Unix/Linux. The previous version was a main frame monolithic version that we would of neither had the time or resources to customize and build.

5.1.2 Minix Microkernel OS and Minix Files or Database

The biggest obstacle was the closed compiled code and licensing and open source was the solution. Minix Microkernel OS and Minix Files or Database were available for customization and the two other requirements met with customization using C and microkernel.

“Tanenbaum was changing the architecture of what is now a microkernel based Unix/Linux. The previous version was a main frame monolithic version that we would of neither had the time or resources to customize and build.”

FIG. 1 APPNET APP1 SETUP

5.1.3 Industry Vertical APP1

Even identifying an industry or vertical in 1987 was challenging as you had to use the 1987 SIC Industry Codes which were the not in any searchable form. NAICS Classification online did not happen online until 2002. SIC was used to understand the build requirements to comply with each industry including information fields at that time. APP1 was 7361 Employment Agencies from the SIC Industry Codes.

5.1.4 APP Source Code Repository

To create a server that could hold different industry verticals needed its own source code repository for each APP or industry vertical. Different app and reader versions for each industry vertical. A package for the Employment theme was created.

The new OS was customize (the Minix OS with C) and recompiled. Tested and working without glitches. Next customization of the Employment and for new APP themes.

5.1.4 First ASP Vertical 1987–1988

The first step was to build the backend for the first vertical to test and master one industry.

5.2. USENET versus APPNET

The platform was designed for Usernet and Minix using a PS/2 PC server with Microkernel. The focus was to deliver multiple connections to a shared database for universal login. A Users script for each Theme or vertical.

In a very primitive manner this would deliver information for a specific industry verticals as required in the Usernet version and a new Minix OS called “MinixAPP version 1.0.” Work on the AppNet Application Server functions was next.

A custom script was created using Usenet as a node that would allow customization of unique fields for each Theme. The First Theme was named APP1. The new distribution or syndication system was given the name of AppNet.

A backup and user code repository was created which had the files to download and install Minix APP OS 1.1 as well APP1 Usenet Reader using UUCP named “succinet”.

The Minix OS was again rewritten to respond to the new commands. A simple working version and application services platform called AppNet.

5.3. Config Files & MINIX-APPNET-APP1.0 Commands

5.3.1 Basic Customizable Config Files

The appfeed.conf key value, group and peer parameters had to be adjusted to work with a server that had different versions of the APPNewsGroups including:

• appsend.ctl
• appincoming.config
• appreaders.config
• appstorage.config
• appbuff.config
• appoverview.fmt
• appexpire.ctl
• and files that designated moderators.

It was not complex just time consuming. It created unique readers for each APP to be created in AppNet with unqiue appreaders.config files.

The first “Theme Package” APP1 code repository “Employment Descriptions and Listings” was called succinc-emp-1.0.

5.3.2 New “Minix App 1.0” APPNET Commands

Append ”APP” to the beginning for Application commands for all Themes.

APPLIST — retrieve a list of “application newsgroups” available on the server

APPGROUP — select a specific “application newsgroup”

APPARTICLE — retrieve an “job description and listings” from a Usenet server

APPNEWSGROUPS — receive a list of “application newsgroups” created after a specific date and time

APPNEWNEWS — receive a list of “job description and listings” created after a specific date and time

APPNEXT — go to the next message in the “application newsgroup”

APPPOST — post a message or reply to an existing one

APPIHAVE — tell the server the client has an “job posting” it may want

Account APP Owner Controlled → APPSENDME — returned list of “job Q&A postings” not yet posted (Moderation)

5.4. Account, User, Makefile, UUCP Data Sync

5.4.1 Account

The next step was to create a script for an account. It required Theme Managers to have access to the OS & AppNet Theme Files and update Job Descriptions much like Newsgroups. So the script was simple and followed the UUCP CNEWS Usenet protocol and format.

5.4.2 APPNET Profile

Create APPNET Account with UUCP Network ID

>Settings>AppNet-Server>Host Address>Port Number

Login APPNET

Select APP Account UUCP Network ID or Hostname “appnet”

Create or Select Login

>Settings>App>Host Address>Port Number

Send Username

Send Password

5.4.3 APP Profiles

Create or Login Sub APP Accounts with UUCP Hostname “appnet”

>Settings>App>Host Address>Port Number

Create APP Username

Create APP Password

5.4.4 Makefile & UUCP

Makefile.in was designed for each Theme to have unique folder installation based on CNEWS with unique directories.

The UUCP commands were used to sync files between systems and Users for that Theme Package.

Users included AppNet Users and AppNet Accounts. Registered AppNet User Account’s had permission to change Job Descriptions in AppNet Global Data Store which would use UUCP to transfer and copy. AppNet used the HoneyDanBer UUCP which was later used by SunSolaris Servers.

5.4.5 The ASP Gateway

The first task was initiating and connecting the dial up modem and terminal to the UUNET network. UUCP sites through Usenet newsgroups provided this function. Using ExecPC BBS and dial up BBS Terminal access to the pieces were available to server to access and sync and register users with copy with UUCP and create a the Custom Usenet Reader App of Theme.

After the custom OS Theme was added using template libraries “C” to create the custom Minix OS the gateway repository was ready for apps and data stores with common APPNET Account & APP User profiles.

5.4.6 The First Industry Vertical — Employment Job Descriptions & Listings

The gateway or ASP gateway was designed so users could simply setup a new Theme User Profile vertical using code uploaded from the repository or design and start a new vertical such as Insurance.

“The server was built in less than six months. A hard drive upgrade was compatible after days of working with DIP switches. Two 16-Bit 56k modems were integrated to sync networks and Users. The solution was part of the Micro Channel technology called “Bus Mastering”. With bus mastering, each card could talk to each other directly. Maynard L. Dokken”

FIG. 2 APPNET SERVER — MICRO CHANNEL TECHNOLOGY

5.5. Critical Structural Developments

5.5.1 MCA (Micro Channel Architecture)

Two very important structural changes allowed the project to proceed, sockets Tanenbaum was using in his C programming of Minix Microkernel and the foundations of micro channel support.

There were many pieces needed to make this work. The only hardware that would work was the IBM PS/2 at the time being sold at a discount even with micro channel bus. The only version at the time that had the micro channel architecture (“MCA”) was the 286 version rebuilt into a server box and installed the updated Minix APPNET OS 1.1 or APPNET 1.1.

The IBM PS/2 was Micro Channel Architecture (“MCA”) versus the simple 16-bit AT ISA bus was a critical development. It could support multiple modems on the same PC server. The PC/2 with Intel 286 processor with MCA was only released in 1987 and not easy to find or get.

5.5.2 Micro Channel

Micro Channel was the solution and provided rotation of the cards with 12 milliseconds busts. This was long enough to permit the systems to work with the bus and buffer inbound data from over-runnable devices including hard drives.

Next collision arbitration overcome by the engineers at IBM meant it could have multiple bus-master support and improved arbitration to share the system so bus-master-capable devices could talk directly to each other (peer to peer) at speeds faster than the system CPU, without any other system intervention. This was a solution that was easier said then done. It allowed the project to create the protocol for peer to peer versus CPU processes.

The Hayes Modems were tested for DSL and Dial-Up. UUNET founded in 1987 was one of the largest Internet service providers and one of the early Tier 1 networks based in Northern Virginia. One of the first commercial Internet service providers being used and adopted through the University networks. UUCP was setup to make this work.

5.5.3 Minix File System Database

We were lucky to have the Minix File System available Open Source as well the Open Source Minix 1.0 Microkernel to customize. Minix APP OS 1.0 connected through the modems and synced data using UUCP script commands for APP1 & BBS.

This simple file system was integral to making this work. It provided us what we needed to deliver a very basic Q&A using our APPNET Server. It was a philosophy as much a model for development of a complete solution. It also provided us a model to create an APPNET global user and APP sub account user.

We could now create almost any application we wanted and our minds never stopped. We could deliver the knowledge needed for Users to access, download and start using. We had a backend that provided Accounts for enterprises to sync their data with the Users. Developing the next generation application was always going to be a work in progress. It also provided a future, pushing us to develop many pieces that became a more mature product and service eventually within a companmy called Milinx.

5.5.4 APP1 — Employment & Recruitment Server Theme

APP1 was a custom APPNET account type. It was based on a new Minix APP OS 1.0. It used a custom script download based on the type of account the User selected. It was both a User Account and a script installed on the Users computer. The account Themes were downloaded on diskettes listed as “part 1 — x” and installed on the Users computer using diskettes.

It was a new day for applications and security was only an idea. The platform was open. The listings were open. Access was open. The only part the User needed was a computer and connection and basic Unix skills.

5.5.6 Usenet Reader Script

A unique Usenet Reader Script was created and required for unique output with a set of fields and commands that made it possible to use a unique APPNET Application in 1988. APP1 or succinc-emp-1.0 was being tailored to fit the Employment Listing and Recruitment market. The framework could be customized to fit any market or industry vertical.

Anyone with UUCP Unix access could download the APP1 User Scripts and Reader which provided them two components APP1 and BBS access. The Usenet Newsgroups UUCP “appnet” provided a Network ID so users could find the server and login to an APPNET global account.

Fig. 3 APPNET USER WITH Q&A SHARED BBS ACCESS

5.6. Account & User Login

The first “Theme Package” APP1 in our code repository was “Employment Descriptions and Listings” succinc-emp-1.0 which included the Shared Profile & Data Repository setup.

5.6.1. User

Login APPNET

Select APP Account UUCP Network ID or Hostname “appnet”

Create or Select Login

>Settings>App>Host Address>Port Number

Send Username

Send Password

5.6.2. Create Username

Create Password created a backup code repository which had the files to download and install Minix APP OS 1.1 as well APP1 Usenet Reader using UUCP named “succinet”.

Users included AppNet Users and AppNet Accounts. Registered AppNet User Account’s had permission to change Job Descriptions in AppNet Global Data Store which would use UUCP to transfer and copy. Users could also Post using APPPOST and Read Q&A using the same commands as succinc-emp-1.0. The Q&A were incorporated into the Application in this build.

APPLIST — retrieve a list of “application newsgroups” available on the server

APPGROUP — select a specific “application newsgroup”

APPARTICLE — retrieve an “job description and listings” from a Usenet server

APPNEWSGROUPS — receive a list of “application newsgroups” created after a specific date and time

APPNEWNEWS — receive a list of “job description and listings” created after a specific date and time

APPNEXT — go to the next message in the “application newsgroup”

APPPOST — post a message or reply to an existing one

APPIHAVE — tell the server the client has an “job posting” it may want

5.6.3. User Login

The User would find APPNET “appnet” login and using uuname list known UUCP sites on the network. Create an app account or login and upload the files for individual Theme packages. The login would also provide access to the dial up BBS through the APPNET server using a shared Minix user profile and data store.

5.6.4. Q&A Access

Account APP Owner Controlled → APPSENDME — returned list of “job Q&A postings” not yet posted (Moderation)

5.6.5. Reader

The APP1 commands allowed the user to find the information they needed. The commands were simple and worked within the Minix APP OS 1.0 or APPNet.

The first “Theme Package” APP1 in the code repository was “Employment Descriptions and Listings” succinc-emp-1.0.

APP was appended to the beginning of all commands for all Themes. All was prepared for the launch of APP1 and could be easily customized at any time for the next Theme.

APPLIST — retrieve a list of “application newsgroups” available on the server
APPGROUP — select a specific “application newsgroup”
APPARTICLE — retrieve an “job description and listings” from a Usenet server
APPNEWSGROUPS — receive a list of “application newsgroups” created after a specific date and time
APPNEWNEWS — receive a list of “job description and listings” created after a specific date and time
APPNEXT — go to the next message in the “application newsgroup”
APPPOST — post a message or reply to an existing one
APPIHAVE — tell the server the client has an “job posting” it may want

APPSENDME — returned list of “job postings” not yet posted

5.7. Makefile, UUCP Data Sync

5.7.1. MakeFile

Makefile.in was designed for each Theme to have unique folder installation based on CNEWS with unique directories. This is also how the Shared Profile & Database Directories & Libraries were defined.

5.7.2. UUCP

The UUCP commands used to sync files between systems and Users for that Theme Package also synced the BBS Q&A.

5.8. ASP

Origin of ASP SaaS (APP1) and ASP PaaS (APPNET)

The use of existing UUNET with APPNET (SuccessInc customized USENET) and UUCP provided the backbone to sync accounts and files. Bulletin Boards and Users only needed to login to one single system to access all resources.

The provision of a SuccessInc Software APP Theme Repository was easy access to new customized themes for the UseNet Reader. The customized Minix OS provided multi channel access to the server. The Minix File System of Database provided a single access point for files and user access and controls. APP1 was the first theme for Employment Recruitment.

A working ASP and SaaS platform in 1988. It would evolve into the universal online access platform used by AssuredCard, AssuredCredit and Milinx to build many new technologies. It was the beginning of a new model for online application services and single point user access that many others customized to create new product technology offerings.

The ASP Microsoft used for ASP.net

It should be noted as ASP.NET Core was released on June 27, 2016 as Active Server Pages, or ASP.net Microsoft web pages framework the transition from ASP to SaaS, PaaS and IaaS had begun. Within this research paper you will notice references to SaaS, PaaS and IaaS for greater clarity on which part of the ASP services each development is related.

6. Results

6.1. Overview

Maynard Dokken’s contributions to the tech world started with his work on SuccessInc, arguably the first operating ASP. This provided the business community with a model for software applications over the Internet, a revolutionary idea in the late 1980s and the early 1990s. Earlier, firms often depended on their infrastructure, and, more often than not, it proved expensive and needed the services of IT professionals. The ASP model that Mr. Dokken presented erased these barriers and made it possible for small companies to use software that would otherwise be too expensive. This idea is the forerunner to what is now called Software as a Service (SaaS).

Maynard’s vision for SuccessInc was to create a platform where businesses could remotely manage operations like recruitment, inventory, and other essential functions. His innovation, APP1, was the first fully functional online recruitment service that allowed companies to manage job listings, applicants, and interviews over the Internet. This early innovation demonstrated the potential of the ASP model, illustrating how businesses could streamline operations through internet-based services.

The evolution from ASP SaaS and PaaS to todays products and services marked a significant technological leap. While ASP services provided companies with software via a centralized server, SaaS and PaaS allowed companies to not only access software but also to scale their operations efficiently. In SaaS, the software is delivered and maintained by a third party, removing the need for users to install or manage software locally. In PaaS the platform is delivered and maintained by a third party, removing the need to managing and maintaining the equipment.

This shift in service models, initiated by pioneers like Dokken, paved the way for modern SaaS, PaaS and IaaS platforms, which are now integral to business operations globally.

6.2. Key Technologies

Several critical technologies emerged from SuccessInc APPNET and APP1. The advent of the Microkernel from Mainframes. One was the ability to login to several networks and bulleting boards with one server. The other was a repository for the reader of which APP1 at this time in history. Another was the ability to use two networks with one system. The multi channel bus or micro channel achitecture (“MCA”) was developed using an open source Minix OS and C. It did not exist in 1988 and was custom programmed by SuccessInc. There were many other innovations that enabled this system to operate and connect including the creation of UUNET UUCP architecture for launch of the APPNET to access multiple sources of data with one system login.

The ASP or APPNET recruitment process was efficient and a scalable to handle job postings on a national or globally networked basis. To, track applicants, and manage recruitment workflows. APP1 was a pioneering example of how Internet services could reduce the need for paper-based operations, freeing businesses from cumbersome administrative tasks.

In the transition to SaaS, the focus moved from simply providing software as a service to creating platforms or PaaS that allowed companies to customize, scale, and integrate their software environments. Platforms like Salesforce and others follower this model by offering users the ability to expand software functionalities based on their specific business needs.

Maynard Dokken’s foresight in creating a scalable, service-oriented model architecture helped influence these transitions to service oriented architecture and products. The success of Mr. Dokken’s ASP model allowed businesses willing to embrace cloud-based services to set the stage for the widespread adoption of SaaS and PaaS platforms in the coming decades.

6.3. Historical Comparisons

Research into comparable services revealed SuccessInc, using all documentation verifying these developments including AssuredCard, AssuredCredit and Milinx, were all ahead of similar firms in all sectors.

Below are examples of publicy available information and sources which apply as much to SuccessInc as to Milinx almost a decade later.

7.0 Origin of ASP SaaS and ASP PaaS

7.1. ASP (Application Service Provider) and SaaS

7.1.1. Overview

Maynard Dokken’s contributions to the tech world started with his work on SuccessInc, one of the first ASP firms. ASP provided the business community with the opportunity to use software applications over the Internet, a revolutionary idea in the late 1980s and the early 1990s. Earlier, firms often depended on their infrastructure, and, more often than not, it proved expensive and needed the services of IT professionals. The ASP model that Dokken presented erased these barriers and made it possible for small companies to use software that would otherwise be too expensive. This idea is the forerunner to what is now called Software as a Service (SaaS).

Dokken’s vision for SuccessInc was to create a platform where businesses could remotely manage operations like recruitment, inventory, and other essential functions. His innovation, APP1, was the first fully functional online recruitment service that allowed companies to manage job listings, applicants, and interviews over the Internet. This early innovation demonstrated the potential of the ASP model, illustrating how businesses could streamline operations through internet-based services.

The evolution from ASP to SaaS marked a significant technological leap. While ASP services provided companies with software via a centralized server, SaaS allowed companies to not only access software but also to scale their operations efficiently. In SaaS, the software is delivered and maintained by a third party, removing the need for users to install or manage software locally. This shift in service models, initiated by pioneers like Dokken, paved the way for modern SaaS platforms like Salesforce and Microsoft 365, which are now integral to business operations globally.

7.1.2. Key Technologies

A critical technology that emerged from SuccessInc was APP1, which transformed the recruitment process by offering companies an efficient, scalable way to handle job postings, track applicants, and manage recruitment workflows. APP1 was a pioneering example of how Internet services could reduce the need for paper-based operations, freeing businesses from cumbersome administrative tasks.

In the transition to SaaS, the focus moved from simply providing software as a service to creating platforms that allowed companies to customize, scale, and integrate their software environments. Platforms like Salesforce and Microsoft 365 build on this model by offering users the ability to expand software functionalities based on their specific business needs. Salesforce, for example, provides customer relationship management (CRM) tools while also enabling integrations with external software. This flexibility and scalability represent the evolution of the ASP model into today’s SaaS frameworks.

Dokken’s foresight in creating such a scalable, service-oriented model helped influence this transition. The success of SuccessInc’s ASP model showed that businesses were willing to embrace cloud-based services, setting the stage for the widespread adoption of SaaS platforms in the coming decades.

7.1.3. Legacy

The ASP model implemented by Dokken revolutionized the business environment, especially for SMEs changing their approach to business. Before the availability of ASP services, SMEs had a rather negative outlook in the business world because purchasing enterprise software and managing onsite structures was very costly to them. ASP services allowed SMEs to compete with large organizations due to services such as remote access to software.

This transition to SaaS went even further in this regard. Due to the subscription service delivery model, SaaS platforms greatly reduced the entry threshold for organizations that wanted to implement innovative solutions. Organizations could now transact at a level of service required, thus helping them control expenditure. Today, SaaS is widely accepted as a fundamental part of business processes; more and more organizations of all sizes use cloud solutions for various purposes — from customer relationship management to internal communication.

The legacy of Dokken’s work on ASP and SaaS can be seen in the vast number of SaaS platforms available today, offering solutions for almost every aspect of business management. The model he helped pioneer has democratized access to software and continues to fuel innovation in the tech sector.

7.2. Hosted Online Payment Gateway

7.2.1. Evolution of Payment Gateways

Maynard Dokken has made a few contributions to the field of online payments, including one of the first online payment systems, AssuredCard. In the mid-1990s, as the commercial usage of the internet started to emerge, there was a rising need for safe and efficient means of executing financial transactions electronically. The conventional banking industries lacked efficient structures to address the intricacies of Internet-based deals, an area that pioneers such as Dokken aimed at serving.

The AssuredCard system was the first to come up with a secure and effective way of making credit card payments over the Internet. The four most significant innovations of AssuredCard were identified as the company’s dual-network security system. This architecture isolated transactional operations from financial data, or in other words, it had two levels of security. Here, users only dealt with the graphical user interface to conduct their transactions while the real information processing occurred on a hidden back-end network. It greatly lowered the probability of hacking and created a new benchmark for safe web transactions.

The idea of AssuredCard, which was to be developed by Dokken, was to provide a system that would be both secure and fast as well as easy to use. Consequently, the platform offered features like the automated clearing house (ACH) transfer that can enable businesses to make payments without many middlemen and more swiftly. These innovations helped in the formation of advanced online payments such as PayPal and Stripe which are expanding from the essentials articulated by the early participants like Dokken.

7.2.2. Technological Details

The AssuredCard system utilized Novell/NT systems, a robust network infrastructure designed to handle the demands of real-time transaction processing. This infrastructure allowed the system to process transactions quickly and efficiently, even as the volume of online payments began to grow exponentially. The use of ACH transfers was another key innovation. ACH transfers are payments made through the automated clearing house network which is much more efficient and secure than check payments or credit card payments. Incorporating ACH capabilities into the platform made it possible for Dokken to get the capacity to handle thousands of transactions in a short span without major disruptions in the security and performance of the system that is inherent in the usual handling of transactions in the payment system.

Another critical aspect of the AssuredCard system was its use of data encryption to protect sensitive financial information. Encryption made it possible that even though data was transmitted through the network, nobody else would understand what was being relayed. This level of security was important during the initial years of e-commerce as there were so many cases of fraud and data theft. The encryption methods employed by AssuredCard set the standard for secure online payments and influenced later innovations in financial technology.

Dokken’s implementation of these technologies demonstrated a deep understanding of the security challenges posed by online payments. His ability to create a system that balanced security with efficiency helped AssuredCard gain traction as one of the most reliable online payment platforms of its time.

7.2.3. Legacy

The legacy of AssuredCard is evident in the continued evolution of online payment systems. Platforms like PayPal and Stripe, which dominate the online payments industry today, owe much of their success to the early innovations pioneered by systems like AssuredCard. Both PayPal and Stripe utilize dual-network architectures, encryption technologies, and ACH transfers — core features of the AssuredCard platform.

For instance, PayPal has embarked on the development of other services beyond what AssuredCard offered it by adding peer-to-peer payments, subscription payments, and cross-border payments. However, Stripe has been keen on building a platform that developers will love by making it easy for business people to incorporate payment processing on their websites and mobile applications. Security is still important to both companies, using encryption and separating the networks to protect the user’s money information.

Another proof of the use of Dokken’s work in understanding AssuredCard is the increasing importance of financial technology (fintech) in the current market. A growing number of fintech firms are finding new methods of handling payments, handling financial information, and protecting financial transactions. Many of the principles introduced by early systems such as AssuredCard are still followed in these innovations to ensure that the payments made over the internet are secure, effective, and open to users all over the world.

This means that through Dokken’s efforts, the necessary conditions for the emergence of a modern fintech market were created. By solving the security and efficiency problems of electronic transactions, he set the ground for today’s multi-billion-dollar online payment processing system that drives the e-commerce world.

7.3. Mobile App Development & Wireless Infrastructure

7.3.1. Mobile Apps: Infrastructure and Development

Maynard Dokken made a great contribution as a leader to the mobile app infrastructure, especially the one for real-time interactive applications. Another of the great initiatives during Dokken’s leadership was the creation of the TTS IVR (Text-to-Speech Interactive Voice Response). This system changed the way that businesses engaged with customers because it was voice-activated replacing manual interaction with voice responses. TTS IVR was developed to undertake extensive customer service-related activities including processing and responding to numerous inquiries and enhancing customer relations without requiring human intervention (Dokken, 2024). This technology began shaping and became popular in industries including telecommunications, e-commerce, and banking the most because there was high pressure to offer customer services and fast.

In addition to TTS IVR, Dokken’s team developed the Mobile Messaging Application Protocol (MMAP) and Simple Messaging Application Protocol (SMAP). These protocols were key to the rise of mobile messaging services, facilitating real-time communication through mobile apps and allowing businesses to notify customers about important updates or promotions instantly. With MMAP/SMAP, businesses could engage directly with customers, improving both operational efficiency and customer experience. The use of these protocols for mobile messaging has now become standard across industries, particularly in banking and telecommunications, where customers require immediate alerts on account activities or service updates (Milinx, 2001).

Together, TTS IVR, MMAP, and SMAP formed the backbone of modern mobile app infrastructure, transforming how businesses communicate with their customers. These developments allowed companies to deliver more personalized, efficient services while automating many previously manual tasks. The widespread adoption of mobile apps across various sectors can trace its roots to the foundational work done under Dokken’s leadership, which allowed mobile platforms to become a central hub for real-time notifications, messaging, and interaction.

7.3.2. Wireless Infrastructure: ASP Wireless and Notification Networks

While mobile app infrastructure was vital, Dokken’s work extended into the realm of wireless infrastructure, particularly with the design of ASP Wireless Infrastructure and a Notification Network. Wireless communication systems were still developing when Dokken envisioned a solution that allowed businesses to operate more efficiently by sending real-time notifications through a cloud-based system. This wireless network enabled companies to manage alerts, operations, and customer communications without relying on outdated manual processes.

The ASP Wireless Infrastructure and Notification Network provided companies with the ability to monitor and manage their operations remotely, a capability that was especially useful for industries that required constant communication with clients, such as healthcare, telecommunications, and logistics. With this system in place, businesses could offer services such as instant banking alerts, package tracking updates, and real-time inventory management, ensuring they stay connected with customers and other stakeholders at all times (Milinx, 2001).

The significance of Dokken’s wireless infrastructure lies in its long-term impact on modern telecommunications. The foundation laid by the ASP Wireless Infrastructure was integral to the development of mobile networks and real-time notifications that are now crucial to modern applications. Today, wireless systems such as push notifications and real-time alerts are used in banking apps to notify users of transactions, in e-commerce to track deliveries, and in healthcare for patient monitoring and appointment scheduling. Dokken’s innovations enabled businesses to offer better, faster services while improving the user experience through instant communication (Milinx, 2024).

7.3.3. Technological Influence on Modern Services

The effectiveness of Dokken as an IT consultant is seen in the fact that today virtually all industries utilize real-time communication in mobile app development and wireless infrastructure. For example, current banking applications involve the use of push notifications, and immediate messaging for transaction alerts, low balance, and fraud. These services are built on the foundation laid by technologies like TTS IVR, MMAP, and SMAP, which first enabled such direct interaction between businesses and their clients. Similarly, the Notification Network developed under Dokken’s leadership has become a key component of today’s digital landscape, with industries such as telecommunications and logistics utilizing these networks to streamline operations and maintain instant communication with customers.

7.4. Financial Technologies

7.4.1. Biometric Encryption

One of Dokken’s most significant contributions to financial technology was the development of biometric encryption. This advancement marked a new level of security for cloud services and SaaS models. At a time when computer break-ins were on the rise, biometric encryption became an answer to the problem since it relied on personal physiological characteristics like fingerprints or retinal scans for the protection of data. This technology made it secure that personal data stored in a cloud could only be retrieved by an authorized user reassuring cloud-based system (Dokken, 2024).

Biometric encryption was of special significance in industries dealing with sensitive information like health, finance, and government. With biometric authentication being … incorporated into more business and institutional processes, data privacy could be enhanced and fraud as well as violations of the regulations could be prevented. At present, biometric encryption is implemented in various applications, starting with mobile banking applications and ending with healthcare information systems, to protect personal information that cannot be protected with the help of password-based protection systems.

7.4.2. Universal Meta-Database API

Another of Dokken’s key innovations was the creation of the Universal Meta-Database API, which revolutionized how businesses and financial institutions exchanged data. The API framework also enabled businesses to link many databases irrespective of their platform, to enhance data sharing. Before this innovation, the process of data management and data exchange across various systems was a real challenge, which led to various problems and data isolation (Milinx, 2001).

The Universal Meta-Database API solved this problem by standardizing data access, allowing companies to integrate various data sources and platforms more effectively. For financial institutions, this meant improved data sharing between banks, payment processors, and regulatory bodies. The API framework not only improved operational effectiveness but also improved data protection by ensuring that as information was being passed from one platform to another, it was secure (SuccessInc, 2024). This innovation is still evident in the finance and e-commerce industries where APIs are used in all aspects of payment processing to customer account management.

7.4.3. Hosted Cloud Operating System: Universal miDesktop

Dokken’s influence also extended to cloud-based business operations through the development of the Universal miDesktop Operating System. This cloud-based operating system allowed businesses to access a virtual desktop environment without needing physical installations on-site. The Universal miDesktop provided companies with the flexibility to scale their operations without incurring the high costs associated with traditional IT infrastructure (Milinx, 2001).

By eliminating the need for local hardware and software installations, the Universal miDesktop made it easier for businesses to manage their operations remotely. It was especially helpful for SMEs who required maximum productivity while working with minimal capital. The hosted operating system also improved security since data could be treated and saved in a safe virtual cloud as opposed to the physical hard drives. Today, cloud operating systems like Google Workspace and Microsoft 365 have become essential tools for businesses, and Dokken’s early work on the Universal miDesktop helped lay the groundwork for these systems.

8.0. Adoption

8.1. Following Success

ASP SuccessInc, AssuredCard and AssuredCredit merged into Milinx

It should be noted that Milinx Business Group, Inc., launched in 1997 merged the work of 12 years into a single entity with the name a derivative of Minix, the Unix OS used to develop the original ASP SaaS PaaS server in 1988.

It should also be noted that companies who followed and adopted this model were slow yet successful in the implementation of this new model and idea. Most of these entrants launched these models almost two decades after SuccessInc and a decade or more after Milinx.

Adobe (transitioned to SaaS 2011–2013)

• Founded: 1982
• Market Cap: $250.9B
• Revenue: $19.4 billion

Description: Adobe has successfully transitioned from a traditional software company to a SaaS powerhouse. Its Creative Cloud suite, which includes popular tools like Photoshop and Illustrator, is widely used by creative professionals worldwide. Adobe’s Document Cloud and Experience Cloud have also seen significant growth, catering to digital document management and customer experience needs respectively.

Microsoft (transitioned to SaaS 2008–2010)

• Founded: 1975
• Market Cap: $3.42T
• Revenue: $211.9 billion

Description: Microsoft has become a leader in cloud computing with its Azure platform. The company’s Office 365 suite has transformed traditional office software into a cloud-based subscription service. Microsoft’s diverse portfolio includes enterprise solutions, gaming (Xbox), and hardware (Surface devices), making it one of the most valuable companies in the world.

Salesforce (2003 SaaS and 2007 PaaS)

• Founded: 1999
• Market Cap: $244.6B
• Revenue: $34.8 billion

Description: Salesforce pioneered the SaaS model with its CRM platform. The company has expanded its offerings to include marketing automation (Marketing Cloud), e-commerce (Commerce Cloud), and analytics (Tableau). Salesforce’s focus on customer success and its AppExchange marketplace have contributed to its continued growth and market leadership.

Intuit (transitioned to SaaS 2010–2014)

• Founded: 1983
• Market Cap: $173.44B
• Products: QuickBooks, TurboTax, CreditKarma, MailChimp

Description: Intuit has successfully transitioned its financial software products to the cloud. QuickBooks Online has become a leading accounting solution for small businesses, while TurboTax dominates the online tax preparation market. Recent acquisitions of CreditKarma and MailChimp have expanded Intuit’s reach into personal finance and email marketing.

NetApp (transitioned to SaaS 2015–2016)

• Founded: 1992
• Market Cap: $27.23B
• Focus: Data storage solutions

Description: NetApp specializes in cloud data services and data management. The company has evolved from a storage hardware provider to offer a range of cloud-based data services, including hybrid cloud solutions, data protection, and AI-driven data management tools. NetApp’s focus on helping organizations manage and leverage their data in multi-cloud environments has positioned it as a key player in the modern IT infrastructure landscape.

Amazon (PaaS services starting 2006)

• Founded: Amazon S3 was launched on March 14, 2006, as one of the first publicly available AWS services.
• Market Cap: approximately $1.98 trillion as of October 2024
• Focus: AWS PaaS

Description: AWS is a comprehensive cloud computing platform providing on-demand cloud services to individuals, companies, and governments on a metered, pay-as-you-go basis. S3 the object storage service designed for storing and retrieving any amount of data from anywhere on the internet. S3 stores data as objects within buckets. An object consists of a file and optional metadata, while a bucket serves as a container for objects. The service provides a simple web services interface that allows developers to store and retrieve any amount of data, at any time, from anywhere on the web

Milinx (SaaS, PaaS and IaaS from 1997–2001 now MilinxAI)

• Founded: 1997
• Market Cap: Privately held, valuation not publicly disclosed
• Focus: SaaS AI Automation

Description: Milinx from its roots was an early pioneer and ASP or SaaS PaaS provider. The company developed many innovations during its short history including a patents for technology for online payment gateway, ecommerce integration with remote infrastructure services, secure networks for accessing network clients, wireless mobile apps and notification, and much more.

The new Milinx direction is now AI. Some of the companies following this direction are below and as follows:

8.2. Transition to AI

Google DeepMind

• Founded: 2010 (as DeepMind), acquired by Google in 2014
• Market Cap: Part of Alphabet Inc. (GOOGL), which has a market cap of $1.73T
• Focus: Artificial Intelligence research and applications

Description: Google DeepMind is at the forefront of AI research and development. Known for breakthroughs like AlphaGo and AlphaFold, the company is pushing the boundaries of machine learning and AI applications. DeepMind’s work spans various fields, including healthcare, scientific discovery, and game theory. As part of Google, it contributes to enhancing AI capabilities across Google’s product suite and tackles complex global challenges.

Databricks

• Founded: 2013
• Market Cap: Privately held, valued at $43B (as of September 2023)
• Revenue: Estimated $1.5B (2023)

Description: Databricks is a data and AI company that provides a unified platform for data engineering, machine learning, and analytics. Their Lakehouse Platform combines the best elements of data warehouses and data lakes. Databricks is known for its contributions to open-source projects like Apache Spark and Delta Lake. The company serves a wide range of industries, helping organizations leverage big data and AI to drive insights and innovation.

Inflection AI

• Founded: 2022
• Market Cap: Privately held, valued at $4B (as of June 2023)
• Focus: Conversational AI and large language models

Description: Inflection AI is a relatively new player in the AI field, focusing on developing advanced conversational AI systems. Founded by DeepMind co-founder Mustafa Suleyman and LinkedIn co-founder Reid Hoffman, the company aims to create more natural and context-aware AI interactions. Their flagship product, Pi, is an AI assistant designed for open-ended conversations and problem-solving.

CrowdStrike

• Founded: 2011
• Market Cap: $46.85B
• Revenue: $2.24B (2023)

Description: CrowdStrike is a leader in cloud-delivered endpoint and workload protection. Their Falcon platform integrates AI, machine learning, and behavioral analytics to provide real-time threat detection and prevention. CrowdStrike’s SaaS model allows for rapid deployment and scalability, making it a preferred choice for organizations seeking advanced cybersecurity solutions. The company’s focus on threat intelligence and proactive security measures has positioned it as a key player in the evolving cybersecurity landscape.

Domino Data Lab

• Founded: 2013
• Market Cap: Privately held, valuation not publicly disclosed
• Focus: Enterprise MLOps platform

Description: Domino Data Lab provides an enterprise MLOps platform that helps data science teams accelerate research, deploy models faster, and collaborate more effectively. Their platform supports the entire data science lifecycle, from ideation to production. Domino Data Lab caters to various industries, including finance, healthcare, and manufacturing, enabling organizations to scale their data science and machine learning initiatives. The company’s emphasis on reproducibility, collaboration, and governance in data science workflows has made it a significant player in the growing field of MLOps.

MilinxAI (formerly Milinx was a SaaS and PaaS in 2000–2001)

• Founded: 1997
• Market Cap: Privately held, valuation not publicly disclosed
• Focus: SaaS AI Automation

Description: MilinxAI, evolving from its roots as an early ASP provider, is now at the forefront of AI-driven SaaS and PaaS solutions. The company is developing innovative AI models to automate business processes, including supply chain management and promotion. This next-generation approach aims to create a new paradigm in SaaS and PaaS, leveraging artificial intelligence to enhance efficiency and decision-making across various business operations. This also includes a patent pending technology for protection of AI and SaaS-PaaS systems and AI users.

These SaaS and PaaS AI industries have seen tremendous growth, with companies like Adobe bringing in $12.95B in Annual Recurring Revenue (ARR) from SaaS products in Q2 2022. This history showcases the transformation from early ASP models to modern SaaS and PaaS AI-driven platforms, highlighting the industry’s shift towards customer-centric, scalable, and cloud-based solutions. The future of SaaS, PaaS and AI continue to evolve, with a focus on advanced analytics, AI integration, personalized customer experiences, and solving complex global challenges.

9. Discussion

9.1. Challenges Faced

Mr. Dokken was a pioneer in shaping modern cloud computing, SaaS (Software as a Service), Platform as a Service (PaaS) and mobile or wireless ASP IaaS (Infrastructure as a Service). Through work in ASP, mobile app platforms, biometric encryption, and hosted cloud systems introduced innovative models that transformed the technological landscape. Maynard’s visionary approach to solving complex technological challenges helped businesses reduce operational costs, enhance accessibility, and drive efficiency. Despite the departure of Maynard Dokken from Milinx these contributions remain influential in today’s financial systems and cloud-based solutions.

9.2. Patents Abandoned

After the resignation of Maynard Dokken one of the major setbacks that Milinx faced was the inability to maintain its patents, particularly for the universal payment gateway. Although the technology had initially proven successful, the new management struggled to keep pace with the rapidly evolving tech landscape. Instead of continuing to focus on innovation and cloud services, the company shifted its resources toward less competitive technologies, particularly primitive hosting. The patents were not invalidated due to external threats but rather lost because the new leadership failed to properly maintain and support the technological innovations that had been developed under Dokken’s leadership.

Contrary to some accounts, Milinx’s failure was not simply a result of typical market challenges faced by high-tech businesses in the early 2000s. During Dokken’s tenure, the company had acquired over 30,000 users, demonstrating strong demand for its cloud-based services. The real downfall occurred after the company’s strategic shift away from innovation to focus on primitive hosting services. The loss of patents and the decline of the company’s technological value were direct results of poor management and a deviation from the original vision (Milinx, 2001).

This mismanagement, coupled with a lack of strategic foresight, left Milinx vulnerable. After Dokken’s exit, the company’s inability to uphold the cutting-edge development of the payment gateway system led to the loss of its competitive advantage. While new entrants in the market built on ideas originally pioneered by Milinx, the company’s value diminished as it was unable to further develop or protect its original innovations. This failure compromised Milinx’s prospects for growth and significantly weakened its capital base, halting its plans to expand the business and introduce new products and services (Dokken, 2024).

10. Conclusion

After reviewing all the material I can confirm that it provides an accurate and comprehensive overview of the history and evolution of Application Service Providers (ASP), Software as a Service (SaaS), and Platform as a Service (PaaS) from 1988 to 2024. This paper highlights several key points and milestones in this technological journey:

10.1. Early Foundations (1988–1996)

SuccessInc, founded by Maynard L. Dokken, developed one of the first ASP systems in 1987–1988.

This pioneering system combined:

• IBM PS/2 server with Microkernel Architecture
• IBM PS/2 server with Micro Channel Architecture
• Customized MINIX operating system called “Minix APP OS 1.0” or “APPNet 1.0”
• UUCP for networking
• Custom Usenet-like protocol called “AppNet”

This early system demonstrated key concepts that would become central to SaaS and PaaS, including remote application access, centralized data storage, multi-tenant architecture, and industry-specific application packages.

10.2. ASP SaaS and PaaS Evolution (1996–2001)

Milinx Business Group, Inc., launched in 1997, played a significant role in the development of ASP SaaS and PaaS:

• Developed the Milinx Managed Application Platform (MMAP™) in 2000
• Partnered with Sun Microsystems, Oracle, and iPlanet
• Created a customizable portal interface for clients
• Filed numerous patents in areas such as biometric encryption and voice context e-mail
• Grew to over 125 employees and exceeded 30,000 active users by December 2001

Milinx’s Early Offerings

Milinx Business Services, Inc. was an Application Service Provider (ASP) that offered a complete suite of rented software applications, including:

1. Milinx Portal Suite
2. Milinx Communicator Suite
3. Milinx CRM Suite

These product suites were designed to enable companies to operate more efficiently and economically in a secure environment with a remote scalable backend.

Key Features of Milinx’s Offerings

Milinx’s approach to software delivery had several innovative aspects:

1. Rental Model: Milinx rented applications stored on its own servers to businesses and individuals for a monthly fee.
2. Cost Reduction: This model reduced the cost of software usage and cut implementation time for new software and hardware from months to weeks.
3. Frequent Upgrades: The SaaS model allowed for regular updates and improvements.
4. IT Staff Reduction: By providing best-of-breed applications, Milinx virtually eliminated the need for large, expensive internal IT staff.

Expanded Product Offerings

Milinx’s three main product suites were augmented with additional offerings:

• miStore: An electronic storefront solution
• miContent: A content management solution
• miOffice: A virtual intranet solution
• miMessaging: A unified messaging solution
• miNetwork: A Virtual Private Network (VPN) solution
• miStorage: An e-storage solution
• miPay: A hosted payment gateway

miBilling: A payment gateway billing application

Innovation and Development

Milinx was actively involved in research and development, with numerous patents pending in areas such as:

• Biometric encryption
• Voice context e-mail
• Voice recognition
• Virtual call center environments

The company was also developing a customizable vertical niche portal interface for its clients, aiming to create electronic communities within a secure ASP space.

Market Presence

By the early 2000s, Milinx had achieved significant market presence:

• Over 30,000 Active Users: Milinx had exceeded 30,000 active users, indicating substantial adoption of their SaaS offerings.
• Strategic Partnerships: The company formed alliances with major technology providers like Sun Microsystems and iPlanet Technology.
• Industry Standards: Milinx launched an ASP Data Center that set industry standards in all of SaaS, PaaS, IaaS and more.

While Salesforce had become more widely recognized in the history of SaaS and CRM thereafter, Milinx’s early and comprehensive SaaS and PaaS offerings demonstrate that the model was already in operation during the mid 1990s and within a scalable architecture in the early 2000s well before any other firm.

10.3. Technological Innovations

The document highlighted several technological innovations by Milinx:

• Development of miDesktop OS using Sun Microsystems Servers, JavaBeans & Cisco Networking technology
• Implementation of high-speed ASP wireless infrastructure services
• Use of biometric threshold security and encryption technology
• Integration of text-to-speech and voice command capabilities

10.4. Market Strategy

The document outlines Milinx’s market strategy, including:

• Targeting three initial market segments: Milinx ASP (SaaS, PaaS, IaaS) Resellers, Business/Internet Consultants, and ASPs/ISPs/Next Gen Telcos
• Focusing on the Small Office/Home Office (SOHO) and Small to Medium Enterprises (SME) markets
• Implementing direct and indirect sales channels

10.5. SaaS and PaaS Expansion and Maturation (2006–2015)

The article accurately describes the entry of major players into the SaaS and PaaS market using the technoogy and foundaions of SuccessInc, AssuredCard, AssuredCredit and Milinx

10.6. Accuracy of Research Paper Claims

The article accurately presents the historical development of ASP , SaaS, PaaS and IaaS evolution, including lesser-known early pioneers such as SuccessInc, AssuredCard, AssuredCredit and Milinx. It correctly notes that these companies were offering ASP, SaaS, PaaS and IaaS solutions before more widely recognized firms like Salesforce, Google and Microsoft.

This research paper also provides a comprehensive and accurate overview of the ASP , SaaS, PaaS and IaaS evolution from 1987 to 2024. It successfully highlights both well-known industry leaders and lesser-known early pioneers, offering a balanced and informative history of these technological transformation.

10.7. Notes to Research

The document covers several key points:

10.7.1. Origins and Evolution

The document traces the origins of cloud computing and SaaS from 1960s time-sharing systems to the mainstream adoption in the 2010s.

It highlights key developments such as:

• The emergence of Application Service Providers (ASPs) in the late 1980s and 1990s
• SuccessInc creation of the first ASP system in 1988
• The application of the SuccessInc framework to AssuredCard for creation of an online payment system and CRM
• The use of the technologies developed from 1988 to 1997 by AssuredCredit for development of a hosted online payment gaterway with eCommerce serivces from 1997 until merged into Milinx
• The rise of SaaS and PaaS in the early 2000s, pioneered by companies like Milinx and later Salesforce
• The launch of Infrastructure-as-a-Service (IaaS) offerings, including Milinx’s services in 2001 and Amazon Web Services in 2006
• The development of Platform-as-a-Service (PaaS) offerings, with Milinx’s solutions in 2001 and later entries like Google App Engine around 2008.

10.7.2. Leadership of Milinx Business Group, Inc.

The document provides extensive details about Milinx’s contributions to the ASP, SaaS, PaaS and IaaS industries by Milinx with the acquisition of the technolgy developments of its predecessors:

• Milinx was established in 1997 as a project and incorporated in December 1998.
• It merged all work from the previous years in SuccessInc, AssuredCard and AssuredCredit when it began active operations in February 1999.
• The company developed and implemented Saas, PaaS and IaaS services from 1997 for various markets, including: Resellers, Business/Internet Consultants, ASPs/SaaS/PaaS/IaaS, ISPs, Next Gen Telcos and other Service Providers (SP)
• Milinx positioned itself as a Systems Mobile Application Provider (S/MAP), developing proprietary software and hosting applications in its data center
• The company launched several innovative products and services, including the Milinx Managed Application Platform (MMAP™), Universal Conversion Service (UCS), and miPORTAL including for vertical or niche sectors

10.8. Recent Developments and Future Outlook (2020–2024)

The SaaS, PaaS and IaaS industries continue to evolve, with a focus on advanced analytics, AI integration, and personalized customer experiences.

10.9. Accuracy and Verification

The information presented is supported by multiple sources, including SEC filings, company news releases, televised interview with Milinx CEO Maynard L. Dokken, archived website screeshots and more. The document appears to be a factual and well-researched account of Milinx’s role in the early development of cloud computing and SaaS, PaaS and IaaS platform and technologies including wireless.

11. Citations

[1] https://successinc.net/

[2] https://www.twst.com/

[3] https://www.sec.gov/Archives/edgar/data/1088815/000109690600000256/0001096906-00-000256.txt

[4] https://milinx.co/news/milinx-launches-data-center-sets-asp-standards

[5] https://en.wikipedia.org/wiki/Salesforce

[6] https://www.ereleases.com/

On September 29, 2000, Milinx Business Group, Inc. announced that they had selected Tantalus Communications Inc. to accelerate the integration of SMAP (Mobile App Standard) Cross Platform Functionality with Universal ASP Connect and future wireless functionality for Milinx’s proprietary applications.. Key points from this announcement:

• Tantalus was chosen to speed up the integration of Extensible Markup Language (XML) into Milinx applications.
• Tantalus was also tasked with integrating Extensible Stylesheet Language (XSL) into Milinx applications.
• Milinx selected Tantalus for its ability to fast-track application development.
• Tantalus was described as a leading software development house located in Vancouver, BC’s Yaletown area.
• The collaboration aimed to enhance Milinx’s Application Service Provider (ASP) capabilities, allowing them to host software at their Application Data Center and rent it over the Internet on a subscription basis.

This announcement was part of Milinx’s efforts to position itself as a leader in the ASP market, focusing on developing and deploying proprietary business applications through its Milinx Managed Application Platform (MMAP™).The company was actively working on various technologies and services, including:

• Cross-platform and wireless functionality
• Integration of a Universal OS for all current operating systems
• Automated data formatting on its MMAP Platform
• Development of miDesktop and Universal Application Data Exchange.

[7] eReleases https://www.ereleases.com/ and EIN Presswire https://www.einpresswire.com/

The Seattle, WA and Vancouver, BC, October 18, 2000 On October 18, 2000, Milinx Business Group, Inc. announced the upcoming release of four new Web-delivered business software products aimed at small-to-medium enterprises.. These products were set to be added to the company’s lineup in the following month, ahead of their initial projections. The four new products announced by Milinx included:

• Server
• Storage
• Network Subscription Services

These web-based applications were developed using Java and were to be ported to an Oracle 8i Database, ensuring high-volume transaction handling, stability, and security. Milinx planned to host these proprietary solutions at their wholly-owned Application Data Center and deliver them to small businesses over the Internet on a subscription basis.

Key Features and Benefits

1. Cost-effective alternative: Milinx positioned these products as a more affordable option compared to traditional “software in a box” solutions..
2. IT spending control: The subscription model was designed to help businesses contain the explosive growth of information technology spending.
3. Web services architecture: Maynard L. Dokken, a representative of Milinx, stated that the technical direction of building these proprietary applications would be based on Web services..
4. Platform-independent: The use of Web services allowed for the construction of distributed Web-based applications in a platform-independent object model.
5. Open standards: The applications were based on open Internet standards such as Extensible Markup Language (XML).
6. Interoperability: Milinx planned to use Simple Object Access Protocol (SOAP) with XML as the underlying structure, allowing for maximum interoperability and full integration of all future Milinx offerings..

Future Developments

Milinx also outlined plans for future developments, including:

• Integration of a Universal OS for all current operating systems
• Automated data formatting on its MMAP Platform
• Development of miNETWORK, miDRIVE, and miWEBVOICE
• Import/Export capabilities for accounting and address books

These announcements demonstrated Milinx’s commitment to providing innovative, web-based business solutions for small-to-medium enterprises, leveraging emerging technologies and standards to offer cost-effective and scalable software products.

[8] Business Wire https://www.businesswire.com/portal/site/home/

On August 30, 2000, Milinx Business Group, Inc. (OTCBB: MIXBA) announced the completion of their Milinx Managed Application Platform (MMAP™). This platform marked a significant milestone in the company’s strategy and positioned Milinx as a leading Application Service Provider (ASP).

Key Features of MMAP™

The Milinx Managed Application Platform was designed to be robust, scalable, and reliable, offering several benefits:

• Enabled clients to define, customize, develop, automate, and manage business processes over the Web
• Ensured lower cost of ownership and rapid time to profit
• Adhered to an open standard architecture
• Provided continuous uptime for critical business applications
• Managed rapid growth through high scalability

Technical Aspects

MMAP™ incorporated several advanced technical features:

Dynamic, fail-safe, advanced application partitioning

Enhanced load balancing capabilities

Content caching and connection pooling for improved performance

Role-based security through access control lists

The platform was supported by premier network suppliers, including Sun Microsystems, Oracle, and iPlanet (a Sun|Netscape Alliance).

Integration with Other Milinx Technologies

MMAP™ was designed to work seamlessly with other Milinx technologies:

• Complemented the Milinx Application Data Center clustered environment
• Utilized a Universal OS or miDesktop with Netscape Crossware and Oracle COBRA technology for the front-end UI
• Incorporated the Milinx OS Database Exchange Protocol built into the Universal OS and Oracle 8i

Applications and Services

Milinx used MMAP™ to host, manage, and deploy its proprietary and ‘best of breed’ software applications, including:

1. miDESKTOP: The central hub for Milinx hosted software
2. miMESSAGING: Unified messaging
3. miCUSTOMER: Customer Relationship Management
4. miSALES: Sales force automation
5. miCOMMERCE: Marketing and e-commerce
6. miCATALOG: Product and inventory management

The completion of MMAP™ positioned Milinx as a foremost ‘pure play’ ASP in the market, enabling the company to move faster in delivering new, custom, and proprietary software solutions to its clients.

[9] eReleases https://www.ereleases.com/ MarketersMedia https://marketersmedia.com/

On November 28, 2000, Milinx Business Group, Inc. announced its expansion into the wireless sector with the introduction of Universal Conversion Service (UCS), a software service designed to address the hardware limitations and file format incompatibilities of wireless devices.

[10] https://milinx.co/news/smap-first-universal-mobile-app-connect-and-integration

[11] https://milinx.co/news/data-center-apps-drives-storage-network-subsciption-services

[12] https://milinx.co/news/mmap-integrated-asp-proprietary-applications-platform

[13] https://milinx.co/news/milinx-to-deliver-high-speed-asp-wireless-insfrastructure-services

SEC Edgar Milinx Filings https://www.sec.gov/edgar/search/#/q=milinx&dateRange=all

[14] 10-Q (Quarterly report) 2001–02–20

https://www.sec.gov/edgar/search/#0001.txt

[15] 10-Q (Quarterly report) 2001–05–21

https://www.sec.gov/edgar/search/#milinx10q_march2001.txt

[16] 10-K (Annual report) 2001–11–16

https://www.sec.gov/edgar/search/#milinx10k_june2001.txt

[17] 10-Q (Quarterly report) 2001–12–21

https://www.sec.gov/edgar/search/#milinx10q_sept2001.txt

[18] 10-K/A (Annual report) 2001–12–24

https://www.sec.gov/edgar/search/#milinx10kamend1_june2001.txt

[19] 8-K (Current report) 2001–08–30

Shareholders elected to change President & CEO

[19] Resignation as Chairman of Maynard L. Dokken 8-K (Current report) 2002–01–29

https://www.sec.gov/edgar/search/#milinx8k_jan282002.txt

[21] Reorganization of Milinx after Maynard L. Dokken’s departure 10-Q (Quarterly report) 2002–03–21

[20} https://milinx.co/news/milinx-featured-on-world-business-review

https://cdn.jwplayer.com/players/xI4hSk1S-FDwn3GZD.html

[21] Milinx Data-Center Optimized Applications Security Customer Support Control Intro Video

https://cdn.jwplayer.com/players/xI4hSk1S-FDwn3GZD.html

[22] Maynard L Dokken — Milinx President CEO Milinx ASP Costs Benefits Intro Video

https://cdn.jwplayer.com/players/0OlMUkt5-FDwn3GZD.html

[23] Maynard L Dokken Milinx President CEO Milinx — ASP Helps Business Core Competencies Intro Video

https://cdn.jwplayer.com/players/41qq8r6w-FDwn3GZD.html

[24] Maynard L Dokken, Milinx President & CEO- ASP Future Wireless Intelligent Applications Intro Video

https://cdn.jwplayer.com/players/hnvF0WKb-FDwn3GZD.html

[25] Maynard L Dokken President CEO Milinx ASP Explains Cloud Network Secure Storage Distributed Data Centers Intro Video

https://cdn.jwplayer.com/players/rfGV6LF5-FDwn3GZD.html

[26] Maynard L Dokken on ASP Proprietary Innovation, Patent Protection and Commoditization Solutions Intro Video

https://cdn.jwplayer.com/players/1RDYqGO9-FDwn3GZD.html

[27] Press Release Listings March 7, 2000 to December 7, 2000 https://web.archive.org/web/20001208035900/http://www.milinx.com/company/press.html

[28] Milinx Exceeds 30,000 Users March 8, 2001 https://web.archive.org/web/20001208035900/http://www.milinx.com/company/press.html

[29] Milinx miPortal eCommerce & ASP PaaS Vertical Portal March 20, 2001 https://web.archive.org/web/20010331081547/http://www.milinx.com/company/newsroom.html

[30] Worlds First Hosted Desktop OS March 15, 2001 https://web.archive.org/web/20010526175936/http://www.milinx.com/investor_relations/press/051501.html

• Dokken, M.L. (2024). Breaking the Digital Horizon. Milinx Publishing.
• Milinx (2001). 10K Report, June 2001. Available at: https://www.sec.gov/Archives/edgar/data/1088815/000109690601500480/milinx10k_june2001.txt.
• Milinx (1997). Available at: https://milinx.co/.
• SuccessInc (1988). Available at: https://successinc.net/.
• Patent WO2001067408A1. (2001). Universal Payment Gateway Patent. Available at: https://patents.google.com/patent/WO2001067408A1/en.
• AssuredCard (1994). Available at: https://assuredcard.co/.
• Stripe (2024). Available at: https://stripe.com.
• PayPal (2024). Available at: https://www.paypal.com.

12. References

ASP Industry

https://www.researchgate.net/publication/220035587_The_ASP_Industry_Consortium_Global_Initiatives_and_Market_Impact

ASP Evolution

https://www.researchgate.net/publication/220591092_The_Evolution_of_the_Application_Service_Provider_ASP_Model_Challenges_and_Lessons_Learned

MicroChannel Architecture

https://www.researchgate.net/publication/3188270_Micro_Channel_architecture

MINIX Microkernel OS

https://www.researchgate.net/publication/234806390_MINIX_A_simple_two-process_microkernel

UUNET

https://www.researchgate.net/publication/221554290_UUNET_Technologies_Inc

UUCP

https://www.researchgate.net/publication/220425471_UUCP_Internals

USENET

https://www.researchgate.net/publication/221554764_The_Evolution_of_USENET_News_Systems

ASP Challenges

https://www.researchgate.net/publication/220591092_The_Evolution_of_the_Application_Service_Provider_ASP_Model_Challenges_and_Lessons_Learned

SIC https://www.osha.gov/data/sic-search

UUNET https://en.wikipedia.org/wiki/UUNET

IBM PS/2 https://en.wikipedia.org/wiki/IBM_PS/2

Minix OS https://www.operating-system.org/betriebssystem/_english/bs-minix.htm

Minix Database https://cateee.net/lkddb/web-lkddb/MINIX_FS.html

BBS https://en.wikipedia.org/wiki/Bulletin_board_system

ExecPC https://en.wikipedia.org/wiki/ExecPC_BBS

UUCP https://en.wikipedia.org/wiki/UUCP

UseNet https://en.wikipedia.org/wiki/Usenet

UserNet NewsGroups https://en.wikipedia.org/wiki/Usenet_newsgroup

Andrew Tanenbaum https://www.theregister.com/2024/06/25/tanenbaum_minix_award/

Minix Unix https://en.wikipedia.org/wiki/Minix

Minix (Databse) File System https://en.wikipedia.org/wiki/MINIX_file_system

IBM https://en.wikipedia.org/wiki/IBM

NCR https://en.wikipedia.org/wiki/NCR_Voyix

Xilinx https://en.wikipedia.org/wiki/Xilinx

Microkernel https://en.wikipedia.org/wiki/Microkernel

C Programming Language https://en.wikipedia.org/wiki/C_(programming_language)

NAICS https://en.wikipedia.org/wiki/North_American_Industry_Classification_System

SIC 7361 https://www.osha.gov/sic-manual/7361

Minix APP1 https://successinc.net/asp-appnet-industry-vertical-framework-for-asp-gateway

SunSolaris Servers https://en.wikipedia.org/wiki/Oracle_Solaris

Hayes Modems https://en.wikipedia.org/wiki/Hayes_Microcomputer_Products

DSL https://en.wikipedia.org/wiki/Digital_subscriber_line

Dial-up Service https://en.wikipedia.org/wiki/Dial-up_Internet_access

AppNet https://successinc.net/gateway-operating-system-minix-app-os-1-1-shared-user-account-profile-data

APPNewsGroups https://successinc.net/app1-employment-descriptions-listings-user-login-reader-q-a-access

MCA Micro Channel System Bus https://www.ardent-tool.com/tech/MCA.html

ARPANET https://www.techtarget.com/searchnetworking/definition/ARPANET

NSFNET https://www.nsf.gov/news/news_summ.jsp?cntn_id=103050

Information Security Management Handbook https://engineering.futureuniversity.com/BOOKS%20FOR%20IT/Book%20Information%20Security%20Mangement%206th%20ed.pdf

SunSolaris Servers https://en.wikipedia.org/wiki/Sun_Microsystems

APPNet https://successinc.net/asp-appnet-industry-vertical-framework-for-asp-gateway

APP1 https://successinc.net/app1-employment-descriptions-listings-user-login-reader-q-a-access

Hostname https://en.wikipedia.org/wiki/Hostname

Makefile https://en.wikipedia.org/wiki/Make_(software)#Makefile

Application Service Provider https://en.wikipedia.org/wiki/Application_service_provider

Microsoft https://en.wikipedia.org/wiki/Microsoft

ASP.net

Active Server Pages https://en.wikipedia.org/wiki/Active_Server_Pages

Software as a Service (SaaS) https://en.wikipedia.org/wiki/Software_as_a_service

Software Repository https://en.wikipedia.org/wiki/Software_repository