You are here: Home content generated doc.free bystar PLPC 180014 current NedaBusPlan Neda Open Business Plan

Neda Open Business Plan

Neda Open Business Plan


The Libre-Halaal ByStar Digital Ecosystem
An Inversion to the Proprietary Internet Services Model
Neda Communication Inc.’s Open Business Plan







Document #PLPC-180014
Version 7.0
August 12, 2013





Neda Communications, Inc.
3610 164th Place SE
Bellevue, WA 98008
Phone: (425) 644-8026
E-mail: http://www.neda.com/contact
Web: http://www.neda.com






This document does not constitute an offer to sell,
or a solicitation of an offer to purchase.



Copyright ©2007,2008,2009,2010,2013 Neda Communications, Inc.


Permission is granted to make and distribute complete (not partial)
verbatim copies of this document provided that the copyright notice
and this permission notice are preserved on all copies.



Contents

1  About Neda’s ByStar Open Business Plan

This business plan is about:

The Libre-Halaal ByStar Digital Ecosystem
A Unified and Non-Proprietary Model For Autonomous Internet Services
A Moral Alternative To The Proprietary American Digital Ecosystem

With ByStar, we are creating a complete parallel digital ecosystem to compete with and stand against the existing Proprietary American Digital Ecosystem. Above all, ByStar is about preservation of the individual’s autonomy and privacy.

Neda’s ByStar business model is web published in the form of an Open Business Plan. The plan is freely available on our website to be read by anyone. The primary access page for the ByStar open business plan is:
http://www.neda.com/strategicVision/businessPlan

ByStar open business plan is available in 3 forms:

  • The Condensed Summary (about 12 pages), PDF, HTML.
  • The Executive Summary (about 15 additional pages), PDF, HTML.
  • The Full Plan (about 85 pages), PDF, HTML, PLPC-180014.

1.1  Ambitious, Complex and Unusual

Our business plan is unusual in a number of respects.

  1. What we offer is unique and unprecedent. Our primary offerings are: Tangible Autonomy and Tangible Privacy. On large scale there is a demand for this. Facebook, Google, Microsoft and Apple are in the business of exploitation of autonomy and privacy. The business model required for offering true tangible autonomy and tangible privacy is very different from traditional current practices.
  2. Our Scope and Scale Is Enormous. The scope of ByStar is everything. The “*” in By* comes from the glob expansion symbol. The integrated facilities of ByStar are intended to be used by a very large segment of population on this planet. Attempting something of this monumental scope and scale (a new model for the entire global Internet services industry!) is beyond unorthodox; it’s scarcely even believable.
  3. Our Execution Plan Is Broader Than Business And Engineering. The nature of our offering requires considerations that go beyond engineering, business, marketing and sales. Philosophy, morality, society, social relations and humanity are also on the table.
  4. Our Offerings Demand Internal Transparency Of All Software And Services. It is not possible to offer real and tangible autonomy and privacy without committing to complete internal transparency of software and services. All of ByStar is internally transparent and Libre-Halaal. The proprietary model leads to closed/dark software and dark services (internally opaque) which are inherently anti-autonomy and anti-privacy. By definition, proprietary closed/dark software can not be trusted. So, we take this as a marketing opportunity to attack the proprietary digital ecosystem. And we hit hard.

    Also, it turns out that it is real understanding of the enormous, seismic force of Libre-Halaal software and Services that makes all of this possible.

  5. ByStar Is Already A Reality – It Needs To Grow To Intended Scale. What has already been built is significant. What we want to build is immense. We think big and we execute gradually. Many seeds have been planted. Some flowers are blooming. A lot more remains to be done.

To say that ByStar is very complex and very ambitious would be an understatement. But it is more than plausible. It is viable and likely.

The Business Plan is supported by various websites and services. The primary entry point into the ByStar web collective is www.by-star.net. It is in the form of a “Dear Fellow World Citizen” letter.

The beginings of the Libre-Halaal ByStar Digital Ecosystem is now ready for public exposure. We have been at this for more than a decade. We hope to continue to be at this for a few more decades. So, if you want to dig deep, be prepared to spend some time as a lot is already in place.

1.2  An Open Invitation To Participate

The intended audience and purpose of our plan is very broad. The conventional business plan is intended for a narrow audience: the Venture Capitalists, and for a narrow purpose: to raise capital. But our plan is intended to communicate our business model and invite participation among many constituencies: engineering, business, investment, academia, and those concerned with guardianship of societal liberties.

As a first step, we ask you to review what we have written and built and give us your critique. If you think our work has merit, we also ask you to help us in spreading the word. Please feel welcome to further distribute this document where appropriate.

You can send us your comments, criticisms and corrections through the following
URL: http://www.neda.com/contact.

If you are a qualified investor, the open business plan itself describes further forms of participation, appropriate to the various intended audiences for the plan.

Groups of users (Autonomous ByStarEntities) such as student or staff at a university or High School or a corporation or a church can join ByStar en masse and obtain ByStar services.

In a document titled:

A Strategy For Rapidly Becoming An Internet Application Service Provider
Joining, Adopting and/or Licensing ByStar
A Public Unsolicited Proposal
http://www.by-star.net/PLPC/180040

We describe various options for those interested in joining, adopting and/or licensing ByStar.

Your participation in any and all forms is greatly appreciated. Please accept our thanks in advance!

Neda’s ByStar Open Business Plan

2  Digest - - Condensed Summary

We are building The Libre-Halaal By* (ByStar) Digital Ecosystem, a unified and non-proprietary model for autonomous internet services. ByStar (pronounced “by-star”) is based on the model of Federations of Autonomous Libre-Halaal Services and is being presented as a moral alternative to the American Proprietary Digital Ecosystem.

By “Digital Ecosystem”, we mean the whole thing, including inter-related software, systems, services, content and societal frameworks. The integrated facilities of ByStar are intended to be used by a very large segment of population on this planet. The scope of these integrated offerings is vast – paralleling most of what exists in the proprietary Internet today. The parallels include:

  • A Gmail that recognizes your mailbox must be autonomous and private.
  • A Facebook that respects your privacy.
  • A YouTube that recognizes your content as yours.
  • A Windows that creates a deep Software-Service continuum.

The equivalent of all of these in the ByStar model are unified, consistent and coherent.

Broad and deep usage of these software and these Internet application services will create revenue opportunities that are similar to those of large Internet application service providers today. These revenues include subscriber fees, advertising, customization consultation, general consultation and interaction facilitation fees. Significance and emphasis of these revenues source will evolve.

ByStar is not about any new particular functionality. It is not a faster, cheaper, better story. In terms of functionality, what we offer is generally same as what exists today.

Our primary offerings are: Tangible Autonomy and Tangible Privacy. On large scale there is a demand for this. Facebook, Google, Microsoft and Apple are in the business of exploitation of autonomy and privacy. The business model required for offering true tangible autonomy and tangible privacy is very different from traditional current practices.

Key distinguishing aspects of our approach and software and services are:

  • Preservation of the individual’s autonomy. ByStar services are inherently autonomous. They belong to their owner-user – not the service provier. Optionally, the user can possess the service.
  • Preservation of the individual’s privacy. The individual is in full control of her service. She can fully control her privacy.
  • They are comprehensive, unified, consistent and cohesive. The scope of ByStar is everything. The “*” in By* comes from the glob expansion symbol. And all these services are unified with the ByStarEntity model.
  • They are rooted in the correct manner-of-existence of software and services. The entirety of ByStar software and services are internally transparent. ByStar software and services development process is fully collaborative.

In other words, morality, health of society, and well being of humanity are an intgral part of software and services that we offer. Our work is primarily not Businessman driven. It is Engineer driven.

We believe that privacy, autonomy and freedom aspects of the Digital Ecosystem that we are creating are important enough to “convert” many existing proprietary service users to become Libre-Halaal ByStar users. All attempts at claiming autonomy and privacy in the proprietary model are hollow at most. It is not possible to offer real and tangible autonomy and privacy without committing to complete internal transparency of software and services. The proprietary model leads to dark software and dark services (internally opaque) which are inherently anti-autonomy and anti-privacy.

To the extent that Venture Capitalists are an audience for this open business plan, we know that talking morality to a Venture Capitalist is like talking chastity to a prostitute. From the perspective of a Venture Capitalist, morality per se is of no interest whatever. But the moral dimension is an essential component of our marketing strategy, and from the perspective of an intelligent Venture Capitalist, this is what matters.

And, if any disrespect is ever directed towards Venture Capitalists in any of our communications, it is merely part of the execution of our marketing plan. Only the Venture Capitalist who understands this entangled strategy fully—that being held in contempt as a Venture Capitalist represents an investment opportunity—is a suitable investor candidate for this open business plan.

So, we are claiming to have created a complete parallel Libre-Halaal Digital Ecosystem to stand against and in contrast to the existing Proprietary American Digital Ecosystem. And now we want to make its adoption very widespread.

Such a large undertaking by such a small group should normally amount to not much more than pipe dreams. Typical first reaction to our claim is a chuckle. Some say it is insane. Many say that the notion of creating a parallel digital ecosystem is so very lofty that it can’t be realistic.

We have experienced all of that before twice – with Internet itself and with GNU/Linux (FOSS).

There are several reasons why we believe widespread usage of what we are building is more than plausible. It is viable and likely.

  1. First ByStar ideology is in harmony with nature. We understand the enormous, seismic force that accompanies halaal manner-of-existence of software and halaal manner-of-existence of Internet services (as expressed in the Libre-Halaal label). Manifestations of this force include the Free Software Movement and Linux. But there is far more to come.
  2. We have already built the needed framework and starting points. These are in place and are growing.
  3. The ByStar model grand design is broad, evolutionary, expandable and it can grow to scale to planet wide usage.
  4. The demand for autonomy and privacy are very real. Many are starting to recognize that things like Facebook are very wrong. Healthy alternatives are craved for.
  5. The business and economic models for ByStar have been thought through and are being cultivated.

2.1  Problem: Individual’s Autonomy and Privacy Are Being Crushed

In the Proprietary American Digital Ecosystem (Internet Application Services as they exist today), the individual’s autonomy and privacy are being crushed. A deal has been made. Users free-of-charge get: email, calendar, address book, content publication, and facebook friends. In return, American corporations get: semantic analysis of email, spying with consent, traffic, logs and audit trail analysis and behaviour cross referencing.

A new currency has been created. The user’s autonomy and privacy is now the implicit internet currency. For now, the established business model is that of translation of the individual’s privacy into targeted advertising. That business model will naturally grow in scope. The debit side of this new currency is civilization and humanity.

Today, the world is largely unaware of this. The public is completely oblivious to the perils of the proprietary Internet model, and happily entrusts its personal data, its privacy, its freedoms and its civil liberties to proprietary business interests. And the people whose responsibility it is to safeguard the public interest – government, and the engineering profession – are asleep at the wheel.

We begin by characterizing the existing proprietary digital ecosystem as fundamentally corrupt, and well on its way towards the destruction of humanity. Under immediate threat of destruction are the privacy of the individual, and the autonomy of the individual. There is already the beginning of dawning realization within society of the growing danger to these rights and freedoms. By the proprietary digital ecosystem, we mean the existing digital hegemony of companies like Facebook, Google, Microsoft, Apple, and others. Individually and collectively, we refer to these as the “Proprietary American Digital Ecosystem.” This is to be contrasted with the healthy and Libre-Halaal digital ecosystem that is needed—and that we provide.

The Libre-Halaal ByStar Digital Ecosystem is not theory. A great deal has already been built. The needed framework and starting points are in place. ByStar is growing. Many use it.

To put it in its intended very widespread usage (planet wide), we want your participation.

We now present an overview of our work and the contours of ByStar in 4 regards – Ideology, Model, Capabilities and Economics.

2.2  ByStar Ideology

Digital ecosystems exist within societal frameworks. Digital ecosystems are shaped by societal norms and digital ecosystems shape people and society.

A very important aspect of societal framework which has immediate impact on shape of digital ecosystems are laws and models governing poly-existentials (knowledge, ideas, information, the digital domain). Societal Agreements governing all that is digital (and more broadly poly-existential) in the West is based on the Intellectual Property Rights regime. This has shaped the entirety of Western Digital Ecosystems.

Loss of autonomy and privacy are symptoms of the basic model of the Proprietary American Digital Ecosystem. At societal level, autonomy and privacy can not be preserved just with new technology. There are no band-aid technical solutions that can be applied to the proprietary digital ecosystem that can fix it.

In contrast, ByStar is ab-initio driven by the ideology that morality and health of society should be the foundation of the ByStar digital ecosystem. The fundamental difference between ByStar ideology and the Proprietary American ideology is that in ByStar priorities, society/humanity comes first and profit/economics come second. In the Proprietary American priorities profit/economics comes first and above all else.

2.2.1  Halaal and Haraam and The Libre-Halaal Label

Our focus as engineers is to build the right thing.

We introduce the sensitive and potent word “Halaal.” We define this in the document titled:

Introducing Halaal and Haraam into Globish
Based on Moral Philosophy of Abstract Halaal
http://www.by-star.net/PLPC/120039 — [5]

We precisely define what we mean by “Halaal” and “Haraam” and the explicit context and scope of the “Libre-Halaal” label. We use the word Halaal carefully and consistently to emphasize that our work is anchored in morality.

Briefly, philosophical halaal is “manifestation” of “moral sensibilities” relevant to a specific topic where “the set of actions” map to “right.” And, philosophical haraam is “manifestation” of “moral sensibilities” relevant to a specific topic where “the set of actions” map to “wrong.”

In the “Libre-Halaal” label, Libre indicates that:

  1. The scope of consideration of Halaal is manner-of-existence of poly-existentials.
  2. We reject the Western IPR regime. That the natural right to copy and the natural right to apply knowledge are the basis of our ideology.

Halaal indicates that:

  1. We are rooted in philosphy and morality — Not just economics.
  2. For each form of poly-existential, the manner-of-existence that permit Professions to safeguard society and humanity are the Halaal manner-of-existence for that poly-existential.

2.2.2  Nature of Poly-Existentials: Basis For Abolishment Of IPR

Next we attack the foundation of the proprietary ecosytem: the Intellectual Property Rights (IPR) regime of copyright and patents.

In a document titled:

The Nature of Poly-Existentials:
Basis for Abolishment of The Western Intellectual Property Rights Regime
http://www.by-star.net/PLPC/120033 — [13]

We analyze and discredit the Western Intellectual Property Rights regime based on the inherent nature of what it seeks to control and restrict. All digital constructs are inherently Poly-Existentials. Poly-Existentials are poly-possessable. Assignment of restrictive ownership to what is poly-possessable is in conflict with nature.

The Western Intellectual Property ownership regime does not serve the ideal intended purpose of societal regulations, i.e. to balance rights equitably among conflicting constituencies. On the contrary, it has the effect of enriching a minority of powerful vested interests, to the very great detriment of society at large. The detrimental effects include the obstruction of engineering creativity, a distortion of the competitive business environment, and denial of the benefits thereof to the public.

Many societies fully reject the basic concept of patents and copyright. Yet, the Western Intellectual Property ownership regime is portrayed by Westerners as universal and global. Since poly-existence and digital entities are inherently not restricted by borders, the nature of global Internet demands rejection of the Western Intellectual Property ownership regime.

2.2.3  Libre-Halaal Software – Halaal Manner-Of-Existence Of Software

Next we focus on the correct manner-of-existence of software.

We do this in a document titled:

Libre-Halaal Software
Defining Halaal Manner-Of-Existence Of Software
http://www.by-star.net/PLPC/180044 — [7]

Our definitions for Halaal manner-of-existence of software and Internet service are concrete and precise. These definitions are similar to the “Free Software” and “Open Source” definitions but are distinct. As engineers, our legitimacy for addressing this topic is our responsibility to the engineering profession and the engineering profession’s responsibility to society.

We have created the http://www.HalaalSoftware.org site for further cultivation of the concept of Libre-Halaal Software.

Software (and more broadly Digital-Entities) is Libre-Halaal Software (and more broadly Libre-Halaal Digital-Entity) if it has the following attributes:

  1. Unrestricted Multi-Possessibility. There are no restrictions is possessing the software by anyone who wishes to possess it – There are no restrictions in copying and redistributing copies.
  2. Unrestricted Usage. There are no restrictions for using (running) the software.
  3. Internal Transparency. The source code of the software is available. Unless software is internal transparent, the software can not be trusted.
  4. Proper Authors’ Attribution. The authorship of the software shall not be misrepresented.
  5. Perpetuality Of All Of The Above.

2.2.4  Libre-Halaal Services – Halaal Manner-Of-Existence Of Internet Services

We then introduce the concept of “Libre-Halaal Services” and describe the model for guaranteeing internal transparency of Internet application services in a collaborative environment.

In the document titled:

Libre-Halaal Services:
Defining Halaal Manner-Of-Existence Of Internet Application Services
A non-proprietary model for delivery of Internet services
http://www.by-star.net/PLPC/180045 — [6]

We have formulated a radically new, non-proprietary model for delivery of Internet services.

Internet services are in essence access to remote execution of software. Fundamental Difference between software and service is Possessibility. Possession is personal and increases autonomy. Lack of possession decreases autonomy. Hence, software by nature is less of a threat than internet services are to autonomy.

Libre-Halaal Services are an extension of the principles of Libre-Halaal software into the Internet services domain. They are Internet services that can be freely copied and reused by anyone. The Libre Services model exists in relation to the proprietary Internet services model of Apple, MSN, Yahoo and Google, in an analogous way to how GNU/Linux exists in relation to Microsoft Windows.

We have created the http://www.LibreServices.org site for further cultivation of the concept of Libre-Halaal Services.

2.3  ByStar Applied Model Of Federations of Autonomous Libre-Halaal Services

In addition to being Libre-Halaal, ByStar is based on the Unified Autonomous model.

The Internet Services industry has arisen in a highly disorganized, unstructured way, driven by a multitude of uncoordinated commercial initiatives. The various industry capabilities have been built in an ad hoc manner, based on immediate business expedience, rather than by any sort of overarching engineering design. The result is the Internet Services industry as it exists today: chaotic, non-collaborative, uncoordinated, and falling far short of its true potential.

In contrast to this, the ByStar Digital Ecosystem is based on a coherent, collaborative, scalable, generalized Internet Services model.

Together, the Libre-Halaal Services and ByStar models have enormous implications. The Libre Services development model, and the ByStar unified services model, can transform the Internet completely, from the proprietary and ad hoc model of today into something far more powerful.

The realization of this potential is large, complex and ambitious. It is far too large in scope to be accomplished by any one company acting alone, but instead can only be accomplished as a coordinated industry-wide effort. But the ByStar Libre-Halaal Services model enables precisely the necessary large-scale, distributed, cooperative effort.

In the document titled:

The ByStar Applied Model
Of Federations of Autonomous Libre-Halaal Services
http://www.by-star.net/PLPC/180015 — [2]

We provide an overview of the model and design of ByStar Federation of Autonomous Services.

Based on this model and structures, ByStar services can consistently grow and interact with other ByStar services to provide a rich and healthy environment.

2.3.1  The ByStarEntity Concept

ByStar is based on a set of key abstractions, representing the major real-world entities that must be represented within a generalized web structure. These entities include such things as individual persons, businesses, physical locations, and events. For each such entity we have defined the structures and conventions required to represent, instantiate and name that entity in a unified consistent way, and at a very large scale. We have then defined the major classes of services required to manage these entities, and to allow highly generalized interactions within and among each other.

In the ByStar applied model, a real-world entity type (for example individuals or a physical locations) maps on to a ByStarEntityType. A real-world entity instance maps on to a ByStarEntity. All ByStar services are anchored in ByStarEntity.

Each ByStarEntity can be activated within a ByStarAutonomyAssertionVirtualMachine. The representation of a ByStarEntity in a ByStarAutonomyAssertionVirtualMachine is called a ByStarServiceObject. A ByStarServiceObject maps to a Unix account and a user-id.

ByStarServiceCapability is a set of capabilities that any ByStarServiceObject can be provisioned to offer. The software of the ByStarAutonomyAssertionVirtualMachine determines the possible set of capabilities. These capabilities grow as ByStar grows. The current set of capabilities are enumerated in Section 2.7.

Any ByStarServiceCapability can be bound to and publicly exposed through a registered domain name.

2.3.2  ByStar Autonomous Services

ByStar services are structured in two layers. (1) ByStar Autonomous Services and (2) ByStar Federated Services.

Any ByStar Autonomous Service may also include ByStar Controlled Services.

An Autonomous Libre Services is a Libre Service where the primary user of the service is the “owner” of the service. The concept of Autonomous Libre Services focuses on preserving privacy by providing control over information to users with safe guards of functional transparency, information portability and non-retention controls. Formal definitions are provided in Defining Halaal Manner-Of-Existence Of Software – And Defining Halaal Internet Application Services

Each autonomous Libre-Halaal service is anchored in a ByStarEntity and can offer any of the ByStarServiceCapabilities.

In Figure ?? we present the way that Autonomous Libre Service, Federated Libre Services and User Environments are structured.

2.3.3  ByStar Controlled Services – Internet Of Things

Any ByStar Autonomous Service may control its “ByStar Controlled Services”.

A ByStar Controlled Service is a ByStarEntity which is in control of ByStarAutonomousEntity.

For example, consider an individual (say the author – http://mohsen.1.banan.byname.net) who hypothetically owns a house, a bicycle, a nike fuel band and a tag for his suitcase.

Virtual representation of these could be:

  1. A House – http://info.1-98008-5807-10.bywhere.net – where ByWhere structure links control to its owner (a ByStarAutonomousEntity).
  2. A Bicycle – whose location information goes to it owner (a ByStarAutonomousEntity) and not Google-corporation.
  3. A Nike Fuel Band – which send the exercise information to its owner-individual (not Nike-corporation).
  4. A tag for his suitcase – which links to it owner (a ByStarAutonomousEntity).

Each of these as a ByStarControlledEntity will be controlled by the ByStarAutonomousEntity. All of these are ByStarEntity-s. The ones that are controlled, link to their controller. The ByStarAutonomousEntity has links to all the ByStarControlledEntity-s that it controls.

So, we now have a framework for abstracting individuals as owners/controllers through ByStarAutonomousEntity. And we have abstractions for things to be owned and controlled through ByStarControlledEntity. And we have way a framework for interaction of individuals/things and things/individuals through ByStar Federated Services.

Now, compare the model of ownership and interactions of Things in Libre-Halaal ByStar Digital Ecosystem – which is anchored in the autonomous individual – with the Proprietary American Digital Ecosystem – which is anchored in the Proprietary Corporation. There the proprietary internet service provider controls individuals also through Things.

2.3.4  ByStar Federated Services

Autonomous services and their conrolled services may wish to engage in end-to-end interactions with other autonomous services. But in order to facilitate such interactions, involvement of some intermediary services may be needed.

We refer to such enabling intermediary services as federated services, and we refer to the association of a federated service plus its subscribing autonomous services as a federation of autonomous services.

The concept of Federated Services is layered above Autonomous Services and focuses on interactions amongst Autonomous Services and facilitation of information aggregation amongst ByStar Services.

An example of a federated service for information aggregation is ByTopic.org where autonomously published content (documents/music/video) is optionally centrally republished – autonomous and federated publication are fully consistent.

2.3.5  ByStar Convivial User Environments – Blee and BxGnome

Users experience ByStar Services through ByStar User Environments.

ByStar services can be accessed in a variety of ways. In addition to the traditional browser based model, ByStar provides for rich and deep Software-Service integration.

Initially we are focusing on two convivial, [4], User Environments for ByStar.

Blee (ByStar Libre Emacs Environment) is a layer above Emacs that integrates ByStar platform (Debian GNU/Linux) capabilities into emacs and provides for integration with ByStar Services.

An overview of this User Environment is provided in:

Blee and BxGnome:
ByStar Software-Service Continuum Based Convivial User Environments
http://www.by-star.net/PLPC/180004 — [15]

The deep integration of Libre-Halaal Software and Libre-Halaal Internet Services creates a Libre-Halaal Software-Service continuum, far superior in capability to any Proprietary/Haraam Software/Service combination.

2.3.6  ByStar Content Generation and Content Publication Facilities

ByStar offers a rich environment and a number of facilities for content generation.

Autonomous Content Publication facilities are a well established feature of ByStar.

In the document titled:

ByStar Content Production and Publication Facilities
http://www.by-star.net/PLPC/180038 — [17]

we describe capabilities and features of ByStar content generation facilities and ByStar autonomous content publication facilities.

Autonomous self publication can then be augmented by information aggregation federated services such as ByTopic, ByContent and BySearch.

2.4  ByStar Central

The basic design of ByStar is very distributed. Services are autonomous and interactions are usually end-to-end.

This means that ByStar is centrally light. But there are some fundamental and infrastructural and foundational organizations and services that are required at the center of ByStar.

The following infrastructure and foundational organizations have been put in place towards administration, guardianship, direction setting and facilitation of collaboration and growth of ByStar.

2.4.1  The Free Protocols Foundation – non-profit, non-proprietary

Free Protocols Foundation is the non-profit legal entity that facilitates collaborative development, maintenance and administration of ByStar.

2.5  Neda Communications, Inc. – for-profit, non-proprietary

Neda Communications, Inc. is the for-profit legal entity that has developed Libre-Halaal ByStar Services. The core of ByStar software is subject to the Affero v3 General Public License and also the Neda Commercial License (dual licensed). Neda plans to profit from widespread usage of The Libre-Halaal ByStar Digital Ecosystem in a variety of ways.

2.5.1  LibreCenter.net

LibreCenter.net is Neda’s data center. It is distinct and different from other data centers in that is built purely on Libre/Halaal Software. At this time most ByStar Services are hosted at Libre Center.

2.6  BySource.org

BySource.org is the Software Distribution Center for ByStar software in source form.

2.6.1  ByBinary.org

ByBinary.org is the Software Distribution Center for ByStar software in binary form.

2.6.2  ByStar Name and Number Assignment Authority

ByStar Name and Number Assignment Authority is responsible for central assignment of names and numbers for ByStar services.

Design of ByStar as an ab initio independent separate digital ecosystem permits ByStar to expand beyond the Proprietary American Digital Ecosystem. This is desired and possible for two main reasons. First, ByStar ideology may demand certain separations. Second, end-to-end purity of ByStar software-service continuum enables ByStar to do things that are not possible in the Proprietary American Digital Ecosystem.

ByStar’s Public Key Infrastructure (PKI) and the possibility of a ByStar Alternative DNS Root are some examples.

2.7  Current ByStar Services and Capabilities

ByStar Services are vast in scope. They are designed to be ever growing. Basic structures of ByStar is in place and many services are built or are partially built. The Libre-Halaal Services collaborative framework allows for ByStar to grow dynamically.

Here we provide a summary of where ByStar services stand today.

A snap shot of the organizations, services and software that form the ByStar Digital Ecosystem today are shown in Figure 1.

Free Protocols Foundation central resources are shown in violet in 1. Neda resources are shown in yellow. Current ByStarEntity generators are shown under the “ByStar Autonomous” label and ByStar federated services are shown next to them. ByStar software consists of three major layers, these are shown in blue.

The current status and growth of of ByStar falls into four broad categories:

  1. Current Capabilities of ByStarEntity (ByStarServiceObject) – what any autonomous services is capable of offering.
  2. Current Span of ByStarEntity Generators – What type of autonomous services (ByName, ByArtist, BySmb, etc) can be readily generated and supported.
  3. Current Scope of ByStar Federated Services.
  4. Scale of User Base – how many people are using ByStar?

2.7.1  Current Capabilities of ByStarEntity (ByStarServiceObject)

Every ByStar autonomous service is anchored in a ByStarEntity. Every ByStarEntity can be provisioned to provide any of the current capabilities enumerated below.

  • ByStarEntityIds and credentials – single password. [Unix account based]
  • PKCS – ByStar Public Key Infrustructure (PKI) – Credentials.
  • Autonomous VPN services and ByStar overlay networks. [openvpn based]
  • Large amounts of autonomous disk space. [secure ftp based]
  • Autonomous synchronization and version control facilities. [git – and also svn and cvs based]
  • A Content Management System based website – with both public and private access. [Plone based]
  • A conventional public web-site. [Apache based]
  • e-mail and LibreTexting. [qmail, imap, webmail, etc. based]
  • Content publication services. [Plone based]
  • A photo gallery. [galleria based]
  • Genealogy web services. [geneweb based]
  • Matched User Environment Profile. [Blee based]

Various other capabilities are in the works. With the ByStarEntity model in place, addition of features is quite simple.

2.7.2  Current Status of Span of ByStarEntity Generators

A number of ByStarEntity Generators—the machinery required for fully automated creation of new service instantiations—are in place for a number of ByStarEntityTypes. Current ByStarEntity Generators are shown in Figure 1 under the “ByStar Autonomous” label. We thus have the ability to create unlimited numbers of new accounts in batch mode, or at any time we can “enable” the services, to permit self-service account creation by individual and business users.

In Section 2.7.4, “Growth Of User Base: Timing” we explain the rationale for not having enabled the self-service account creation feature at this time.

2.7.3  Current Status and Scope of ByStar Federated Services

A number of sites are in place for facilitating inter-autonomous relations. Current Federated Services are shown in Figure 1 under the “ByStar Federated” label.

Our initial focus amongst federated service are those used for information aggregation. These include ByTopic, ByContent and BySearch.

2.7.4  Growth Of User Base: Timing

An important consideration is the point at which we will begin to accept the burden of significant numbers of users.

In the case of a conventional service deployment there is typically a major emphasis placed on early and rapid growth of user base, to demonstrate demand and marketplace viability of the service, and lay claim to a particular portion of functional territory. This was modus operandi during the dot con era, where claims of user base numbers were an integral part of spin-and-flip and pump-and-dump model. Some of those attitudes still persist.

However we are not following this standard early proof-of-service approach. This may be appropriate for a conventional new service, where service functionality is the central and most critical issue. But for our industry model play, a different timing strategy is required.

First, as a superset of numerous existing services, proof of service for By* in functional terms is already demonstrated by the Internet Services industry as it exists today. It is far more important to prove the model itself rather than its functional manifestations, and hasty creation of user base does little to accomplish this.

Instead we have provided a coherent and complete description of the model in this and our other documents. The theoretical basis for the model is solid, and this will be clear to anyone willing to invest the time to understand it. In addition a number of working By* implementations are already in place; examples are provided. Though the scale of usage remains small, these are sufficient to demonstrate the viability of the Libre model and the By* design, and the value of the resulting services to paying clients.

But a far more important consideration is that installed base is very costly in terms of maintenance and support, and premature exposure to these costs can jeopardize the more critical work of building the underlying model machinery. Therefore we will not take on the burden of user base until the time and/or context is right for this. This means either that we are fully ready to accept the associated costs of ownership, or that the user base is being taken on in an appropriate context, such as a suitable business partnership.

Under either scenario our strategy is the same: at the right time we will populate the services at large scale by mass creation of By* service accounts for large existing user bases, [19].


Figure 1: Libre Services Supporting Organizations

2.8  Relationship With Existing Realities

The Libre Services and By* models are revolutionary, and can be expected to have a revolutionary effect on Internet usage. But these models are about service development and functionality, not about technological infrastructure. We are not reinventing the Internet protocols, or any other technical aspect of Internet operation.

What is being presented here is not a tear-down and rebuild operation.

Libre Services and By* imply no discontinuity, in terms of either technology or service deployment. The implementation model for Libre Services and By* is wholly evolutionary—there exists a continuous migration path from the proprietary model of today to the Libre model of tomorrow.

2.8.1  Relationship With The Proprietary American Digital Ecosystem

Based on ideology, the Libre-Halaal ByStar Digital Ecosystem fully avoids proprietary software and proprietary services. We simply avoid The Proprietary American Digital Ecosystem.

But, any and all of our services can be used in the Proprietary American model.

The core of ByStar software is subject to the Affero v3 General Public License and also the Neda Commercial License (dual licensed).

In a document titled:

A Strategy For Rapidly Becoming An Internet Application Service Provider
Joining, Adopting and/or Licensing ByStar
A Public Unsolicited Proposal
http://www.by-star.net/PLPC/180040 — [16]

We describe various options for those interested in joining, adopting and/or licensing ByStar.

2.8.2  Relationship With FOSS / FLOSS / FreedomBox Movements

Free and open-source software (F/OSS, FOSS) or free/libre/open-source software (FLOSS) is software that is both free and open source. It is liberally licensed to grant users the right to use, copy, study, change, and improve its design through the availability of its source code. In the context of free and open-source software, free refers to the freedom to copy and re-use the software, rather than to the price of the software.

Libre-Halaal ByStar Ideology and FOSS Ideology have a great deal in common and we closely collaborate with our FOSS brothers and sisters, but the ByStar Libre-Halaal Ideology is distinct.

We invite our “Free Software” and “Open-Source” brothers and sisters to recognize that the “Libre-Halaal Software” model is a more complete model and that the “Libre-Halaal Software” label is a better label.

2.8.3  Active Private Parallel Digital Ecosystems – Example: NSA

What we want to do on very large scale and in the open has been done in medium scale in private.

For instance, the United State’s National Security Agency (NSA) has created a separate parallel private digital ecosystem for its own use. NSA operates the private .nsa TLD; many NSA internal email addresses are of the form username@r21.r.nsa, mirroring the NSA organizational group structure. NSA has a particular ideology for its digital ecosystem which includes a large element of security, confidentiality and secrecy. NSA through use of its own particular software and services has created a complete different environment in parallel to the internet.

Precedence of such private parallel digital ecosystems combined with the proven power of Libre-Halaal software demonstrates that widespread realization of ByStar digital ecosystem is very viable.

2.9  ByStar Economics

Having introduced the Bystar Halaal Digital Ecosystem in philosophical, moral, societal and engineering terms, we now turn our attention to the economic and business dimensions.

We are devout Capitalists. The existing capitalist model for mono-existentials is generally correct, in both philosophical and economic terms. But the extension of the mono-existential capitalist model into the domain of poly-existentials, based on the Western IPR regime, is a grave mistake. Philosophically it is wrong. Societally it is harmful to humanity. And economically it is unstable and vulnerable, since it can be displaced by disruptive business models like ours. The Open Business Plan you are reading explains how this will come about, and how we will profit from this.

2.9.1  The For-Profit Non-Proprietary Quadrant

The notion of a non-proprietary construct, residing and operating within the for-profit sector, is new and different. Historically, the for-profit sector has been closely associated with proprietary ownership of assets. Hence the Internet Services industry as we see it today. Also historically, management of non-proprietary or public assets has been primarily associated with the non-profit sector. Hence the current orientation of the Free Software Movement, operating largely within the non-profit sector.

The Libre-Halaal Services deployment model breaks both these traditions. It represents a radical shift of the Internet Services industry from the for-profit, proprietary quadrant, to the for-profit, non-proprietary quadrant. In this space the entire software for an Internet service remains a communal public resource in the trust of the engineering profession, while service deployment is driven forward by the full force of for-profit commercial motivations.

In the document titled:

The For-Profit and Non-Proprietary Quadrant
http://www.by-star.net/PLPC/120042 — [3]

We provide more details on this topic.

As shown in Figure 2, the By* services are positioned in the For-Profit Non-Proprietary Quadrant For Internet Services.


Figure 2: The For-Profit Non-Proprietary Quadrant For Internet Services

As shown in Figure 2, the By* services are positioned in the For-Profit Non-Proprietary Quadrant For Internet Services. Note that in the non-proprietary layer, re-use and collaboration is far richer than the proprietary layer. For example, in the Software slice, Debian and Ubuntu cross progress. In the Services slice the same can happen. Where for example ByStar and FreedomBox can cross progress.

2.9.2  ByStar Value Chain Analysis

ByStar value chain is a chain of activities that we perform in order to deliver a valuable internet services to the market. It is a high-level model of how we take raw externally developed Libre-Halaal software as input, add value to these software packages through various processes, and sell finished services to our customers.

In Figure 3, we illustrate the bystar value chain on the left column and its inter-mixing with proprietary value chains on the right column.


Figure 3: ByStar Supply Chain Model

Focusing on the right column of Figure 3, notice that “Neda Operated By* Services” establish a direct relationship with Subscribers and Users at the very top. Note that the scope of these internet services is everything – the * in By* – and that the intended scale of these services is planet-wide. By definition, no internet services opportunity can be bigger than that.

The arrows between Neda Services and User/Subscriber in Figure 3 include an element of “Trust, Loyalty and Respect” which is the result of “ByStar Ideology” that we presented earlier. The element of trust and respect is fully absent in the left column. In business terms, Trust and Repect, translate into “stickiness” – where the user is more committed to the service. So, you see, all our investments in ideology are actully also business wise.

All of the ByStar value chain software is Libre-Halaal (Free and Open Source) software. ByStar software in Figure 3 is shown in two different colors.

The software in bright blue represents Debian and/or Ubuntu Gnu/Linux and the specific software packages that we have chosen. These are externally developed open source software packages which are typically subject to the free software GPL license (or similar) which permits their inclusion in proprietary services. This is often refered to as ASP loophole.

The software in bright green is the software that Neda has developed. It is subject to the “Affero General Public License Version 3” (AGPL3) and Neda Commercial License (Dual Licensed). AGPL3 closes the ASP loophole. Any ASP which uses ByStar software must subject its changes and improvements to AGPL3. Those ASPs not wishing to do so, can use ByStar software through the Neda Commercial License.

In the left column of Figure 3, we illustrate a typical proprietary ASP who is incorporating ByStar as part of its services based on the Neda Commercial License.

In this environment the model for implementation of By* service functionality is not one of original software development. Rather it is a matter of selection and integration of already available software packages. Virtually all existing By* service functionality has been created this way—in building By* we have written almost no new software components at all.

Thus we are not so much in the business of software development, as we are in the business of software integration. But the integration of software components to produce a coherent service is far from trivial. We have created a sophisticated technical integration environment for this purpose, called the Neda Libre Services Integration Platform (Neda-LSIP) [1].

Design of LSIP and the ByStarEntity Software Platform recognize the evolution of underlying external software (bright blue) in the ByStar value chain. This is the extraordinary magic of Libre-Halaal software and services: the ability to take things and reuse them at extremely low cost. This is the fundamental growth dynamic of Libre Services, and the powerful generative force that is lacking in the proprietary model. This is the key dynamic that causes the By* Libre Services eventually to surpass the proprietary model entirely in terms of features and functionality.

2.9.3  ByStar Open Business Plan

The exposition above, is the condensed summary of our business plan.

As part of our responsibility to create a viable implementation construct we have fully analyzed the business dimension, and we have formulated the business model in the form of an Open Business Plan, titled:

The Libre-Halaal ByStar Open Business Plan
An Inversion to the Proprietary Internet Services Model
Neda Communication Inc.’s Open Business Plan
http://www.by-star.net/PLPC/180014 — [18]
http://www.neda.com/StrategicVision/BusinessPlan

This open business plan is available in 3 forms; the Condensed Summary (this document – about 12 pages), the Executive Summary (about 15 additional pages) and the full plan (about 85 pages).

Our business plan is viable because we understand the critical dynamics of poly-existentials. The current direction of the Internet services industry does indeed present a grave hazard to humanity, and we will indeed safeguard humanity against this. These extraordinary claims provide a unique and powerful marketing message. And they also happen to be true.

2.10  The Full ByStar Picture

The big ByStar picture is shown in Figure 4. Each of the layers in this figure represents either a conceptual definition (shown in blue), or an actual software/service implementation (shown in orange). Each layer builds on the layers beneath.

Figure 4 can be used as a reading roadmap.

The top layer paper is:

The Libre-Halaal ByStar Digital Ecosystem
A Unified and Non-Proprietary Model For Autonomous Internet Services
A Moral Alternative To The Proprietary American Digital Ecosystem
http://www.by-star.net/PLPC/180016

It describes the totality of libre/halaal software, libre/halaal Internet services, content generation and content publication facilities and societal frameworks that are designed for Preservation of ByStar user’s autonomy, privacy, freedom and health of society. In that document we analyze the stresses and forces acting against the existing proprietary American digital ecosystem, and we identify four critical “tear points,” where the existing proprietary hegemony can be broken, and invaded by the ByStar ecosystem. The execution of this business plan is focused on those four tear points.

Figure 4 shows how the moral, legal, societal, engineering, economic and business dimensions of the ByStar Halaal Digital Ecosystem are layered as described above.

Note the differing characterizations of this layering on the left and right. Both characterizations are valid, but they reflect entirely different viewpoints. The left side characterization is called “The Human Model,” and reflects the philosophical, moral and societal elements of the model. It also identifies the role of the engineering profession in maintaining these elements. The right side characterization is called “The Venture Capitalist Model,” and is very different from the “The Human Model.” The same elements are present, but now represent their significance as part of an investment strategy. Thus the moral and societal concerns within the human model are now viewed as a sales and marketing opportunity. This makes clear that when dealing with Venture Capitalists, issues of morality and societal welfare are not the topic of discussion. In this regard Venture Capitalists need only understand that human beings are in fact concerned with vital moral considerations such as “privacy” and “autonomy,” and that these considerations have powerful sales and marketing consequences. And that our unconventional strategy of overturning their sacred-cow – Copyright and Patent model – gives us a huge competitive advantage.


Figure 4: Reading Roadmap For The Libre-Halaal ByStar Digital Ecosystem

The gigantic picture we have drawn in Figure 4 is a blueprint. It represents a complete framework for collaborative work towards an alternative to the current proprietary digital ecosystem. By aligning ourselves with the natural forces and dynamics of poly-existentials, and by means of large-scale unrestricted collaboration, we can achieve this. And we can collectively save humanity.

3  Executive Summary

3.1  About Us

Neda Communications, Inc. is an Internet Application Services company. We provide consulting and Internet services to small-to-medium businesses (SMBs) and to individuals. We are a one-stop full-service shop—we maintain our own Data Center, and we provide a full suite of services for clients requiring any sort of Internet presence. Our revenues derive from the customary sources: consulting, website development, hosting, and subscriber service fees.

So far, there is nothing unusual about any of this.

But our technological model for delivering services, and our long-term strategic vision, are very different from the mainstream. Our Internet services model is radically different in two respects, each having major consequences. First, our Internet services are based on the free software development model. And second, they are a unified services model. For these reasons our model has the potential to transform the Internet Services industry completely, and become the new model for delivery of Internet services, planet-wide.

But first, a bit of stage setting.

3.2  Setting the stage

Part of the debate about free software is now over, while part continues. The part that is over is any question about the viability of free software as a development model for creating large-scale, complex, relevant software systems. GNU/Linux is a fully viable free software alternative to the proprietary Microsoft Windows operating system, against which it continues to make steady inroads. Mozilla is a fully viable alternative to the proprietary Microsoft Internet Explorer, and is also experiencing steadily increasing usage. These and numerous other free software projects—Apache, Qmail, Sendmail, Bind, Plone, Snort and many others—have now become essential and widely used components throughout the software and Internet industries.

And apart from such well-known and high-profile projects, behind the scenes the free software movement has become a flourishing creative environment, generating a constant stream of new and better software packages, duplicating and surpassing the capabilities of an ever-increasing portion of proprietary software territory.

And the fundamental free software creative dynamic has now also become very well understood: the free software development model allows unrestricted creative reuse of existing assets at essentially zero cost. It is from this dynamic that the free software model derives its tremendous generative power. Free software is thus fully established as a generative engine and an industry reality, and is here to stay.

But the part of the debate that continues is whether or not this has any meaningful commercial dimension. Within the proprietary software domain a powerful revenue-generating engine exists in the form of the traditional software licensing model. But this revenue source is absent under the free software model. In its place there are a number of possible business and revenue models, but in all cases these lack the large-scale repeatability that makes things really interesting from a business perspective.

There thus remains a conceptual gap, a puzzle, about how the powerful generative forces of free software can be turned into a large-scale, repeatable, revenue stream. But this puzzle is now solved. And in this business plan we present the solution.

3.3  The transformation of software into services

The Internet has given rise to an enormous new industry: the Internet Services industry. And within this industry the business and revenue models are quite clear and obvious. The largest and most obvious are the subscription fee model of generalized service providers such as Facebook, and the advertising model of numerous specialized no-cost service providers, demonstrated most spectacularly by Google. Both the subscription fee and advertising models are unlimitedly scalable, thus resulting in the gigantic commercial Internet of today.

But the Internet Services industry of today is a fundamentally proprietary construct. While proprietary service providers can and do make frequent use of free software components within their services, they do not espouse the free software development model itself, and their technical development process remains competitive and proprietary. Though they may incorporate free software components, Facebook and Google are certainly not free software.


Figure 5: Business Ramifications Of Software To Service Transformation

Thus as we look at the software and Internet industries of today we see two largely disjoint cultures. As illustrated in Figure 5 we see the free software domain, with its powerful generative and propagative development model, but lacking any clear large-scale monetization model. And separate from this we see the proprietary Internet Services domain, with enormous revenue and business consequences, but handicapped in scope and scale by its competitive development model.

But now we are witnessing a further transformational event in the evolution of the Internet: a shift of traditional software applications towards a service-based implementation, or what is sometimes called the “transformation of software into services.” And this is the critical event that now solves the free software revenue puzzle. This development unites the generative power of the free software domain with the proven revenue models of the services domain. The transformation of software into services allows the powerful generative model of free software to be invested directly into the powerful revenue model of the Internet Services industry.

4  A New Model for Internet Services

The Internet has given rise to an enormous new industry: the Internet Services industry. This is an intensely dynamic industry, enabling many different types of interactions among people, businesses and information. The Internet is also giving rise to a further technological transformation: a shift of traditional software applications towards a service-based implementation, or what is sometimes called the “transformation of software into services.”

But despite its phenomenal growth, the Internet Services industry of today has two characteristics that greatly limit its capabilities and potential. First, virtually all existing Internet Services are based on the traditional proprietary software model. The solution to this is the Libre Services model, a completely non-proprietary model for delivery of Internet Services.

Second, the evolution of the Internet Services industry has taken place in a highly disorganized, unstructured way, driven by a multitude of commercial ventures and initiatives. The various industry capabilities have been created in an ad hoc manner, based on immediate business expedience, rather than by any sort of overarching engineering design. The result, not surprisingly, is chaos.

The solution to this is the By* family of Libre Services. By* (pronounced “by-star”) is a coherent, scalable, generalized Internet Services model.

Together, the Libre Services and By* models have enormous implications. These two models can transform the Internet completely, from the proprietary and ad hoc model of today, into something vastly more powerful.

We are the architects of both the Libre Services and By* models, and we intend to play a leadership role in this transformation.

4.1  Libre Services

Within the general software arena, the free software movement is well established as a viable alternative to proprietary software. But as yet, the free software movement has no formal presence within the services domain. The Internet Services industry of today exists almost entirely in the form of the traditional proprietary software model.

We have established a radically new, completely non-proprietary model for the delivery of Internet services. We call this the Libre Services model.

Libre Services are an extension of the principles of free software into the Internet services domain. They are Internet services that can be freely copied and reused by anyone. Any company or organization can reproduce and host any Libre Service, either for its own use, or for commercial or non-commercial delivery to others. The Libre Services model exists in relationship to the proprietary Internet services model of AOL, MSN, Yahoo, and Google, in an analogous way to how GNU/Linux exists in relation to Microsoft Windows.

This is a radical departure from the existing commercial model, with benefits that are equally radical and far-reaching. The Libre Services model provides a set of critical freedoms that are absent from the proprietary model. These freedoms have major engineering, societal and business consequences.

In the business arena the Libre Services model allows free entry into the Internet Services market, without any intellectual property barriers standing in the way. The effect of this is to transform the industry from the proprietary model of today, into a truly open model. The industry will be thrown open to an entirely different form of competition, creating major new business opportunities and growth.

For those who understand this model and how to deploy it, the business consequences are enormous.

A complete description of the Libre Services model is provided in the article titled Libre Services: A non-proprietary model for delivery of Internet Services [10].

4.2  The By* concept

Libre Services is a general conceptual model for delivery of Internet services. The By* family of services is an actual realization of this model.

By* is a coherent framework for enabling complex interactions among people, businesses and information. The By* framework is based on a formal engineering design approach. The architectural and design considerations are based on proper engineering discipline, rather than short-term marketing and business considerations.

This is what makes By* different from existing services. By* is a formal model for bringing structure and order to the Internet, at the scale of the entire planet.

By* is based on a set of key abstractions, representing the major real-world entities that must be represented within a generalized web structure. These entities include such things as individual persons, businesses, physical locations, and events. For each such entity we have defined the structures and conventions required to represent and instantiate that entity in a unified consistent way, and at a very large scale. We have then defined the major classes of services required to manage these entities, and to allow highly generalized interactions within and among each other.

The result of this structure and discipline is the By* family of services.

4.2.1  The By* family of services

The By* family includes services oriented towards each type of abstracted entity. There are four services oriented towards individual persons: ByName, ByNumber, ByAlias, ByMemory. The first three of these provide services for living persons, while the fourth is dedicated to preserving the memory of deceased persons. The By* family also includes services oriented towards business entities (BySMB/ForSMB), physical locations (ByWhere), events (ByEvent), and services for publication of information (ByTopic). Last and most important, By* includes a set of services allowing complex interactions among the various types of abstracted entity (ByInteraction).

The By* family of services is described in detail in The By* Concept: A Unified Model for Internet Services [11]. A summary is provided in Table ??. Examples of By* instances are shown in Table 1.

Service Type Domain Name Description
BySMB/ForSMB www.neda.com A software development and Internet services company. An extensive and comprehensive website with over 100 pages. Technologies: Jetspeed, Tomcat, Gallery.
www.NewDinnerware.com An online store selling fine porcelain tableware. Includes standard e-retail features: shopping cart, checkout, credit card payment. Technology: Interchange.
www.TalkToUS.org A non-profit organization promoting better international understanding. Enables communication via short personal video messages. Technologies: Jetspeed, Gallery, streaming video.
www.PinaMotorsports.com An auto repair and specialized auto customization shop. Technologies: Plone/Zope, Interchange, Gallery.
www.Payk.net A non-profit organization for grassroots communication among Iranians. Technologies: Plone/Zope, Gallery.
www.AllMuslimCemetery.org An Islamic cemetery. Related to ByMemory; many gravesites have associated ByMemory memorials. Technology: Plone/Zope.
www.LibreServices.org A non-profit forum and resource center for development of Libre Services. Technology: Plone/Zope.
www.BySource.org A Free Software distribution center.
ByMemory yazdan.1.banan.bymemory.net A memorial site. Includes a genealogy and photo gallery; multilingual. Technologies: Plone/Zope, GeneWeb, Gallery.
ByName mohsen.banan.1.byname.net A personal website for a professional engineer. Includes a genealogy and photo gallery; multilingual. Technologies: Plone/Zope, blog, GeneWeb, Gallery.
ByWhere info.1-98008-5807-10.bywhere.net A ByWhere site used to provide address and driving directions. Technologies: Apache, Gallery.
ForRent.1-98008-5765-05.bywhere.net A ByWhere site used to provide house rental information. Technologies: Apache, Gallery.


Table 1: By* Instance Examples

The By* services are Libre Services, and as such can be freely copied and reproduced by anyone. We have established the BySource and ByBinary software distribution sites to provide the resources required to reproduce any By* service.

For a detailed description of the By* services and how they are different to existing services, see The By* Concept: A Unified Model for Internet Services [11].

4.3  Growth dynamics

The Libre Services and By* models include a set of powerful inherent growth dynamics. These are discussed in detail in The By* Concept: A Unified Model for Internet Services [11]; here we present only a brief summary. By* includes growth dynamics in the following respects:

  • Features and functionality. The growth dynamic in terms of functionality is the powerful generative force of the free software development model. The free software movement is a flourishing creative environment, constantly producing new and better functional software components, and thus assuring ever-expanding features, capabilities and functionality of By*. This potent dynamic will cause By* eventually to surpass all proprietary services in terms of features and functionality.
  • By* deployment by other service providers. Any company or organization can reproduce and operate the By* services for itself, thus becoming an independent Internet services provider. For a company with a large user base and an existing service delivery infrastructure (such as a large ISP, wireless network provider, or telephone company) the business case for this is clear and compelling. The value propositions are: immediate entry into the Internet Services market as an independent service provider, greatly expanded scope of relationship with an existing customer base, and access to a much larger and growing user base.

    Furthermore, the company can accomplish this extremely rapidly, at very low cost, and on the basis of several alternative business models to best fit the company’s positioning and broader business strategies. Thus the growth dynamic for By* deployment by other service providers is the clear business motivation for this.

  • Service usage. By* service usage will increase over time as a result of a number of motivations and influences acting in concert. These include:
    • The inherent merits of the services themselves in terms of protection of civil liberties: privacy, freedom of speech, and freedom of information.
    • The inherent merits of the services themselves in terms of completeness, close integration, and powerful functionality.
    • The ever-increasing richness of features and functional capability assured by the free software and Libre Services development models.
    • The growing societal awareness of these inherent merits, occuring as a result of on-going discussion and analysis, and influencing attitudes and behavior over time.
    • The open and free nature of By*, allowing unrestricted deployment and usage in any desired environment: commercial, non-commercial, government, academic.

    The summation of these and other growth dynamics results in a synergistic, monotonically increasing, grassroots acceptance and usage of the By* services model.

5  About this Initiative

This initiative is highly unconventional in a number of respects.

5.1  Scope and scale

First, the scope and scale of what we are doing is extremely large. This is not about a conventional product or service, as these are commonly defined and bounded. Rather, this is about the reinvention of an entire industry.

Our goal is to establish Libre Services as a new model for the Internet Services industry, and as the eventual replacement for the existing proprietary services model. In effect, this amounts to the creation of a new industry that today does not exist.

The scope of By* is similarly large. While Libre Services can be thought of as a conceptual model and philosophy for delivery of Internet Services, By* is an actual functional implementation of Internet Services. But in terms of functional capability, the scope of By* far exceeds typical Internet services as they exist today.

By* is a unified services model, integrating together the capabilities of numerous services that presently exist in functional isolation. For example, all the functional capabilities of MySpace, Evite and Craigslist are subsumed under ByName, ByEvent and ByInteraction respectively. However, these capabilities are fully integrated with one another within the general By* framework. The result is a far more powerful, coherent and complete services model.

The scope and scale of the Libre Services and By* initatives are thus enormous. The business opportunities are likewise enormous.

5.2  An engineering construct

Second, the Libre Services and By* models are first and foremost engineering constructs rather than business constructs. They are constructed based on formal engineering architectural principles for the design of large-scale systems. They are built to do something, and do it well. They are intended to bring real and enduring value to society at large.

The Libre Services and By* initiatives certainly have important business dimensions. But the business dimensions are a consequence of the engineering merits, not the other way round. This is in contrast to many other recent ventures within the Internet domain, where business imperatives are the driving motivation, to which engineering considerations take a back seat. But in the case of Libre Services and By*, the overriding principle is engineering integrity. The business dimensions derive naturally from creating something of value, that people will pay for.

This is not the first time a construct of this scale and significance has arisen. The best recent example is the World Wide Web itself, conceived originally as a method for sharing electronic information, but turning out to have gigantic social and business ramifications.

But in the past the originators of such constructs have exercised vision and leadership only in the conceptual and engineering domains, while neglecting to consider the business consequences. It has been left to others to recognize and develop, or perhaps exploit and abuse, the business possibilities.

Again the Internet provides a prime example. The Internet reality was created by engineers, who apparently gave little thought to the commercial possibilities. It was left to entrepreneurs and financiers to create the enormous commercial Internet industry, and along the way, turn the true Internet into the false Internet bubble.

Here again is where this initiative is different. We have conceived Libre Services and By* as formal engineering constructs, and we are exercising conceptual and engineering leadership to move these initiatives forward. But we have also recognized the business consequences right from the outset, and we are exercising leadership in that domain too. This Business Plan is part of that leadership.

The emergence of the Internet Services industry, and the accompanying shift of traditional software applications towards a service-based implementation, represent a major transformational event in the evolution of the Internet. This event may well give rise to a second round of Internet hype and frenzy, following the initial dot-com bubble of 1997–2001. Indeed, there is already widespread recognition of the “transformation of software into services” as the next major technological event in the evolution of the Internet, and the buzz has already started.

A period of irrational exuberance based on this will have the same general characteristics as the initial dot-com bubble. It will include a fundamental engineering reality, and genuine end-user value. But as the business dimensions of this reality emerge, the underlying reality will rapidly be overtaken by a vast amount of overblown commercial hype and profiteering, just as occurred for the dot-com bubble.

Libre Services and By* fall precisely into the space where this is likely to occur. But though we may see a second Internet bubble in the “transformation of software into services” arena, Libre Services and By* are not part of the overblown hype. They are the fundamental engineering reality.

5.3  Open and collaborative

But the most significantly unconventional aspect of this initiative is that it is based on openness and collaboration, rather than proprietary ownership.

The free software movement as we see it today is the first manifestation of a much bigger ideological shift: a shedding of the traditional conventions of material capitalism, and the adoption of a new set of conventions based on non-material capitalism. Western capitalistic societies are rooted in the historical conventions and institutions of material products and materially-based services. In the digital domain these conventions appear in the form of the proprietary software model.

But in the digital domain there is a different and better way of doing things. The power of free software derives from a relinquishing of the traditional intellectual property conventions. Instead, free software is based on a set of principles that allow powerful generative forces to come into play. Thus traditional copyright is rewritten in the form of copyleft; ownership of software via patents is relinquished in favor of patent-free protocols and software; self-interested software hoarding via trade secrecy is relinquished in favor of openness and collaboration.

The result is a convention of engineering freedom and collaboration, based on collective pooling of resources. The essential premise is quite simple: in the digital domain there is more to be gained by collective pooling than by individual ownership.

This initiative is about the application of this premise to the domain of Internet services. The resulting open collaborative model brings the enormous generative and propagative power of free software to Internet services.

The open and collaborative nature of this initiative, and its industry-wide scope, are opposite sides of the same coin. In the case of a proprietary software product or service, based on ownership via patents, copyright and trade secrecy, the owning entity can only do what can be accomplished by its own in-house resources. Of necessity, this limits the scope of any proprietary venture to that of a traditionally bounded product or service.

But in the case of a non-proprietary construct such as free software or Libre Services, all such limitations are removed. The construct is now open to participation by anyone, and so can truly form the basis for an entire industry. It is the open and collaborative nature of Libre Services that enables its industry-wide scope.

Conversely, any industry-wide enterprise must, of necessity, be open and collaborative. It is simply not possible to achieve anything of such large scope while constrained within the ownership model of a single entity.

6  About this Business Plan

This Business Plan has been written for the following purposes:

  • For internal clarity. The primary purpose of this plan is to establish clarity and coherence of thinking within the Neda team. This plan is the result of extensive discussion and thinking among ourselves. We have thought through and fully defined every aspect of this project and our execution strategy. This plan captures and documents the resulting team consensus.
  • For public readership. The second major purpose of the plan is to make it available for general public readership. The plan is intended for anyone who is interested in what we are doing and wishes to learn more, or who wishes to participate in any way.
  • As part of a framework for participation. Since this is an open collaborative initiative, the necessary industry-wide collaboration must be properly enabled. To this end we have established a coherent framework for participation, which we describe in the following section. This Business Plan is a component of that broader framework, and plays the role of describing the business dimensions of Libre Services and By*.

    The success of Libre Services and By* requires participation by many constituencies, including among others the engineering community, the business community, and the investment community. This Business Plan is intended to facilitate participation by all these constituencies.

    The primary purpose of a conventional Business Plan is to acquire financing, and that is one of the purposes of this plan too. To that end the plan is intended to enable investment participation. But the investment community is just one among multiple audiences for this plan.

  • To describe the business model. The traditional business model is based on a proprietary ownership model. But Libre Services are completely non-proprietary, and therefore the critical ownership element of the traditional business model do not apply.

    In this Business Plan we describe the key aspects of our business model, including the revenue models, competitive advantages, and end-user adoption models.

  • To describe our execution strategy. In this plan we also provide details of our exection strategy, including the order in which we will develop the various revenue streams, and our marketing and recruitment plans.
  • For recruiting. To execute our plans we will need the participation of talented and experienced people. The Business Plan is part of our recruiting pitch to prospective team members. For anyone interested in working with us, the plan presents the uniqueness and scope of what we are doing. And for people who then choose to join the Neda team, the Business Plan helps to create team cohesion and unity of purpose.

6.1  An open Business Plan

Since our engineering and business models are non-proprietary, there is no need for the close secrecy surrounding a traditional proprietary business model. On the contrary, since this initiative is based on openness and participation, it is necessary to articulate it fully to others.

This includes its business dimensions. Therefore in what we believe is a first in the history of business practice, we are documenting our business model in the form of an Open Business Plan, freely available for readership by anyone. This is completely at odds with customary business practice, but is fully consistent with the open and participatory nature of this enterprise.

This is also largely a Business Plan by reference. We have documented every aspect of this initiative in the form of a number of separate documents. Thus the plan takes the form of a roadmap and directory to these supporting materials. Here we provide a high-level overview of the major concepts, together with references and pointers as appropriate.

7  Framework for Participation

The Libre Services initiative is big and ambitious. Something this big is not accomplished by any single company acting alone. Instead it takes place as a distributed industry-wide enterprise, involving many participants.

In particular this enterprise requires the participation of three major consituences: the engineering community, to build the necessary Libre Services infrastructure; the business community, to deploy and deliver Libre Services to end-users; and the investment community, to finance engineering and business development. To these we may usefully add a fourth: the academic community, to provide analysis and critique of these radical new engineering and business models.

Such diverse participation does not take place in a vacuum. Instead, it is greatly facilitated if there exists an enabling framework for participation. To this end we have established a coherent framework for participation by all relevant constituencies.

7.1  Separation of responsibility: Neda and FPF

The overall Libre Services and By* initiatives include activities which naturally fall under different areas of responsibility.

Engineering development of Libre Services software is a communal activity, and the results of this work are communal industry resources, available for use by anyone. The body of Libre Services software is not owned by anyone, in any restrictive sense. On the other hand, deployment and delivery of supported services for end users is a business activity, and the necessary technical and business infrastructures are owned and operated by commercial entities. Throughout this initiative it is necessary to maintain a clear conceptual separation of these two sets of activities, and where responsibility for each resides.

We have established a separation of responsibility to address this issue. Responsibility for moving this initiative forward is divided between two separate entities:

  • The Free Protocols Foundation (FPF) is responsible for Libre Services, the public side of this initiative. Among other things this includes responsibility for establishing the conceptual definition, creating written materials to articulate and promote the concept, and establishing a framework for collaborative engineering development of Libre Services software. All general industry enabling work is the responsibility of the FPF.

    At the outset, the FPF is also playing a hands-on engineering role, and taking responsibility for creating momentum in the engineering development arena. Under the FPF we are doing the necessary work to create a set of starting-point engineering resources.

  • Neda Communications, Inc. is the creator and owner of By*, the private side of this initiative. We are exercising leadership in the business arena by deploying and operating a set of usable, first-generation Libre Services in the form of the By* family of services. Thus all By*-related work is associated specifically with Neda.

For complete details about the complementary roles of the FPF and Neda see Libre Services: A non-proprietary model for delivery of Internet Services [10]. Complete information about the FPF itself is available on the FPF website at: www.freeprotocols.org.

7.2  Libre Services participation

Under the auspices of the Free Protocols Foundation we have created a framework and set of resources for public Libre Services participation.

The first element of the framework consists of a comprehensive articulation of the concept. Participants need to understand the concept clearly. To this end we have documented the concept in the form of an industry white paper titled Libre Services: A non-proprietary model for delivery of Internet Services [10]. This paper provides a complete conceptual description of Libre Services. For anyone wishing to learn about Libre Services, this is the right place to start.

The creative model for Libre Services is collaborative software development. Such collaborative development requires a proper framework to proceed effectively. Under the FPF we have established the following framework for participation:

  • LibreServices.org. LibreServices.org is the central location and forum for collaborative development of Libre Services. It provides information and resources for developers, and acts as the central repository and distribution point for Libre Services software. The software repository includes automated mechanisms to allow developers to retrieve software components from the repository, then resubmit modified software back into the repository.
  • Starting-point software components. We have done the initial development work to create a set of starting-point, reference software components. These are available for immediate use as the basis for engineering development. Refer to Libre Services: A non-proprietary model for delivery of Internet Services [10] for details.
  • Project-based collaboration model. We have defined a project-based collaboration model, consisting of a set of projects required to move the Libre Services initiative forward. Each project is largely independent and self-contained, and ready to be undertaken by an interested group or organization immediately. This allows efficient, coordinated collaboration on multiple projects in parallel.

    Each project is defined in the form of a Project Document, providing a complete specification for the project. The complete list of projects and Project Documents is provided in a separate article, titled Libre Services: Projects for bootstrapping [8].

7.3  By* participation

Libre Services is general public initiative, being driven forward under the leadership of the Free Protocols Foundation. By* is a private commercial enterprise being conducted by Neda Communications, Inc.

We have created appropriate resources to enable participation in the commercial By* enterprise by prospective business partners, investors, and employees. As in the case of Libre Services, the first and most fundamental requirement is a clear articulation of the concept. Prospective By* participants need to understand the concept clearly. To this end we have documented the By* concept in the form of two documents:

  • The By* Concept: A Unified Model for Internet Services [11]. This paper describes the By* concept and family of services from a technical perspective.
  • The Business Plan. The Business Plan (this document) describes deployment of By* from a commercial perspective.

We have also established a framework for investment participation. This is described later in Section 15, Financing.

8  Revenue Models

The By* deployment offers many potential sources of revenue. The major revenue sources are summarized in Table ??.


Phase I Phase II

Pre-By* revenues BySMB/ ForSMB ByName.net ByNumber.net ByAlias.net ByMemory.net ByName.com ByNumber.com ByAlias.com ByMemory.com ByWhere ByInteraction ByEvent ByTopic By* user environments Registrar Libre Engines, WhiteBerry
Hosting
B




F
Subscriber Services

C



F
Advertising


D D


Transaction fees



D


Franchising
E E E E


Website development & customization
B C




Deployment & software consulting

C



F
Registration processing fees





E
Software licenses






F
Colocation A






Consulting A






Non-revenue


C
E


Table 2: Revenue Streams

The rows of the table list the various forms of revenue by general type, such as subscriber service fees, advertising, consulting, etc. The revenue types are listed in their approximate order of magnitude, long-term. Thus the major revenue sources of web hosting, subscriber service fees and advertising appear at the top, while minor non-recurring sources such as consulting appear near the bottom.

Shaded rows indicate revenue sources that are recurring, and thus of greatest interest. Rows that are heavily shaded indicate “true” recurring revenues, meaning revenues that are repeating, calendar scheduled, contractually associated with a specific customer base, while incurring negligible direct costs. Thus web hosting, subscriber service fees and advertising are the classical Internet revenue sources of this type.

The lightly shaded rows indicate revenue categories that are not recurring in this strict technical sense, since they are not necessarily calendar scheduled, and may not be associated with a specific customer base. Nevertheless these revenue types generate a known, regular, stable revenue stream, again while incurring negligible direct cost. From a business revenue perspective therefore, they have much the same merits as the truly recurring revenue types. The two largest revenue categories of this type are transaction fees, and the service franchising model.

The columns of the table list the components of the overall By* deployment. The components are listed very roughly in their order of expected deployment, starting with BySMB/ForSMB, and ending with the indeterminately scheduled WhiteBerry deployment.

For convenience we will use the term “By<Individual>” to refer collectively to the four services for individuals. Thus By<Individual>= {ByName, ByNumber, ByAlias, ByMemory}.

As shown in the table, each of the By<Individual>services will be provided in the form of two separate deployments: By<Individual>.net and By<Individual>.com. The By<Individual>.net services will be provided to users fully supported and advertising-free. The major revenue stream for this deployment consists of subscriber service fees. The By<Individual>.com services will be provided at no cost to users and without support. The major revenue stream for this deployment consists of advertising revenues.

Each table cell with a letter entry indicates a revenue stream associated with the corresponding revenue category and By* component. Empty table cells indicate that there is no associated revenue, or the revenue source is considered to be relatively minor.

The letters themselves indicate the stage of execution at which that particular revenue stream will be developed, as we describe in detail in Section 9, Execution. Thus A indicates current pre-By* deployment revenues, while F indicates the indeterminate future WhiteBerry deployment.

Everything flagged in the table represents a viable and significant revenue stream. However, the various revenue sources vary widely in terms of how well-characterized they are, and at what point they will be realized. As described in Section 9, our execution plan consists of two broad phases. Phase I consists of the development of revenues that are well-characterized and practical within the near term. Phase II consists of the development of longer-term revenues. Some of these are new types of revenue sources deriving from the By* model, and are less well-characterized at this time.

8.1  Hosting and subscriber services

Hosting and subscriber services refers to the regular fees for supported BySMB/ForSMB and By<Individual>.net websites. Support for business websites is commonly referred to as “hosting,” while support for individual websites is commonly referred to as “subscriber services.” In the table these two revenue types are broken out as separate rows to indicate that one is associated with BySMB/ForSMB and the other with By<Individual>.net, but from a technical standpoint the two operations are essentially the same thing: the management of a website along with all its associated services.

Hosting and subscriber services are the major long-term revenue source for the By* deployment, based on the standard Internet service subscription fee model. The extremely large size of this revenue stream derives from the planet-wide scale of the By<Individual>.net services.

8.2  Advertising

Advertising is also a major long-term revenue source, and is the primary revenue stream derived from the By<Individual>.com, ByWhere and ByInteraction services. There are no regular subscription fees associated with any of these services. The revenue model is the proven Internet advertising model, as exemplified by Google and many other no-cost services.

The extremely large size of the advertising revenue stream again derives from the planet-wide scale of the By<Individual>.com and ByInteraction services.

8.3  Transaction fees

Transaction fees refers to usages of services for which it is usual or appropriate to charge fees, such as classified advertising, job postings, etc.

Transaction fees are a secondary revenue source from usage of the ByWhere and ByInteraction services.

8.4  Franchising

The Libre Services model offers a unique deployment and revenue generation model, not shared by the proprietary services model.

Note that since the By* services are all Libre Services, they can be reproduced and operated as a service by anyone. But not under the By* name. The underlying software is all free software, to be reused as a communal resource by anyone, but the By* brand name and the By* domains (ByName.net etc.) are business assets of Neda. Likewise the operational characteristics of the services, as distinct from the engineering functionality, are defined by Neda. This includes such things as the terms of use, pricing schedule, customer support policies—in fact any aspect of operation or delivery of the service that relates to the relationship between the service provider and the user. All these things are characteristic of the By* brand name, owned and operated by Neda.

One way a service provider can reproduce the By* services is to rebrand them under its own name—for example, the Acme* family of services. There will be AcmeName.net, AcmeNumber.net etc., all delivering functionally identical services to ByName etc., but now these brand names and domains are assets of the Acme Mail Order and Internet Services Company Inc., and the services are delivered under Acme delivery terms and policies. Under this arrangement Acme is wholly independent, having no relationship with Neda at all.

Alternatively, Acme can become a By* franchisee. Under this arrangement, Acme becomes a provider of the By* services, branded as such, and under exactly the same terms and conditions as the By* services provided by Neda.

The services provided by Acme will now be a true clone of the By* services, both functionally and operationally. Any user of the Acme-operated By* services will be assured of receiving services that provide an identical user experience to using the Neda-operated By* services. Just as the patron of a franchised McDonald’s in Beijing is assured of an identical fine dining experience to a McDonald’s patron in Chicago.

Under the franchise operation the entire set of By* services is packaged and provided to an independent service provider, who then provides identical services to a particular demographic or subset of users. There are many situations in which this arrangement is a logical choice for the service provider. For example, a third-world country might have only primitive and undeveloped Internet services available to its consumers. An entrepreneur wishing to provide the far superior By* services to this demographic could franchise the entire packaged set of services, then take responsibility for delivering them to this particular demographic. Note that the inherent hiearchy of the Internet and its domains provides an ideal structure for the creation and management of such franchises.

The franchise operation is a key mechanism for growth of the By* services. Clearly, this is an enormously powerful propagation mechanism. As the By* services gain ground, this will become an increasingly important propagation and revenue model. It is the franchise model that allows the By* services to become truly global. Equally clearly, the financial rewards are enormous for the company that is operating the franchise. As the owner of the By* brand and top-level domains, the franchise model provides another gigantic revenue model for Neda.

The franchise model extends across all revenue-generating members of the By* family, including BySMB/ForSMB, By<Individual>, ByWhere and ByInteraction.

8.5  Website development and customization

For the By* services where a website is supported for an individual person or business (i.e. BySMB/ForSMB and By<Individual>.net), there are three models for setting up the website:

  • Self-service. Under the self-service model, businesses and individuals set up the website on their own on an automated basis, in the same way that user accounts are typically created under the existing proprietary services model. Getting a ByName account is a simple as getting a Yahoo or MySpace account.
  • Neda-assisted. Under the Neda-assisted model, Neda provides basic flat-rate assistance to create websites for business and individual users.
  • Custom development. Under the custom development model, Neda takes responsibility for creating the client’s web presence on a consulting basis. Under this model clients can direct their own specific website development and/or customization requirements.

It is expected that a large proportion of BySMB/ForSMB clients will require custom website development to meet their specific business requirements. The BySMB/ForSMB deployment thus includes a significant website development revenue stream. This is a non-recurring revenue stream and does not scale; nevertheless it plays an important role in our execution strategy as an early stage revenue source.

It is expected that a much smaller proportion of By<Individual>subscribers will require assistance or customization.

8.6  Deployment and software consulting

Deployment and software consulting refers to consulting work relating to deployment of By* components by other service providers. This encompasses a number of situations and scenarios, but these generally consist of two major categories:

  • By*-related consulting. This includes consulting work for clients who are deploying the By* services under any of several business models, either under the By* name, or rebranded as an independent service offering under the client company’s own name. This also includes custom software development work for clients who require specific enhancements or customizations to the By* Libre Engine software.

    This also is a non-recurring, non-scaling revenue stream. But it also plays an important role in our execution strategy, both as an early stage revenue source, and as a mechanism for increasing general By* service deployment.

  • WhiteBerry-related consulting. This consists of consulting and software development support services for clients who are deploying the WhiteBerry mobile messaging solution. This is described below in Section 11.1.1.

8.7  Registration processing fees

One of the unique characteristics of the By* architecture is its hierarchical naming model, based on consistent and extensive use of the Internet domain naming system. This allows the naming and addressing of very large name spaces within the By* structure.

As owners of the top-level By* domain names, this places Neda in the position of allocating subdomain names to entities within the By* structure. Thus in effect Neda is the naming authority for these entitites. This represents another revenue opportunity for Neda, similar to the existing Internet registrar function. There are various registration requirements and responsibilities within the By* structure, including allocation of domains, names, numbers, and certificates.

This is a new type of revenue source for an Internet service provider, resulting from the unique characteristics of the By* concept and architecture. Development of this revenue source is part of our long-term direction statement. A precise business model for managing this revenue source has not been established at this time.

8.8  Colocation

We maintain our own state-of-the-art Data Center to support the By* deployment. All By* services, and also the WhiteBerry mobile messaging services, are hosted at the Data Center. The Data Center is fully capable of supporting deployment of By* up to very large scale. Complete details about the Data Center are provided on the Neda website at:
http://www.neda.com/InternetServices/OurDataCenter/

In addition to the By* services we can also use the Data Center for general colocation services, thus generating an additional recurring revenue stream. Colocation refers to providing only physical support for client servers, including rack space, power, environmental control, security, and network connectivity. Operation and maintenance of the servers themselves remains the responsibility of the colocation client. We can provide colocation services to any company or client who requires this, whether related in any way to Libre Services or not.

The colocation revenue stream is not related to the general By* deployment. But it is recurring, and plays an important role as an on-going self-financing revenue source.

We are always interested in acquiring additional colocation clients. If you have colocation requirements that fit our general working model and philosophy, please feel free to contact us directly.

8.9  Consulting

Consulting refers to general data communications consulting services, not necessarily related to Libre Services and By*. This has been the primary source of company revenue since inception, and continues to support our on-going operations.

As a long-time consulting company we are always on the lookout for the right sort of consulting work. In the context of this Business Plan we are particularly interested in projects that have good synergy with Libre Services and By*. If you have a project that fits well with these strategic goals please feel free to contact us directly.

8.10  Non-revenue

The last row of the table indicates those elements of the By* deployment that generate no or limited direct revenues.

In their initial deployment in Stage C, the By<Individual>.com services will not generate revenues. These will be provided at no cost to users, as a free look-and-see service as an uptake mechanism for By<Individual>.net. The advertising model for By<Individual>.com will not be developed until Phase II.

The ByEvent and ByTopic services provide only limited direct revenues. There are no user service charges or transaction fees associated with these services. The primary purpose of these services is to complete and enhance the overall utility of the By* family, thus generating revenues indirectly. There are potential advertising and franchising revenue streams associated with ByEvent and ByTopic, but these are relatively minor and not shown in the table.

The By* user environments also serve to greatly increase the utility of the By* services. There are no direct revenues associated with this element of the By* deployment.

9  Execution

As noted in the previous section, there is a large number of potential revenue streams associated with By*. This creates a great deal of flexibility in execution. In particular, the execution is highly adaptable to the availability of external financing. With no external financing, the revenues can be developed in a gradual self-financed mode. With full funding the revenues can be developed in a highly parallel and large-scale mode.

The following execution plan describes our execution in a wholly self-financed mode, i.e. assuming no external financing at all. In Section 9.4 we describe how the execution can be adapted to various levels of financing.

9.1  By* deployment schedule

There are many ways to generate revenues from the By* deployment. There are multiple revenue streams associated with this enterprise, and at different points during the development of Libre Services and By*, Neda will generate revenue from all of them.

The multiplicity of revenue streams creates both opportunities and challenges. The challenge is to develop the revenue streams in a logical order. We have formulated a coherent plan for deploying the By* services. We will be developing the various revenue streams in a particular order, based on a number of factors including:

  • Required development and deployment investment to reach revenue returns
  • Magnitude of expected resultant revenues
  • Controllability of deployment—the ability to deploy at a small and/or gradually increasing scale
  • Service support requirements
  • Synergy of functionality among the accumulating family of deployed services

The following execution plan describes the order of By* development and deployment and development of the associated revenue streams. But it should be noted that our execution strategy is highly flexible and readily adaptable to changing industry conditions, availability of external financing, and other future contingencies. The execution roadmap presented below is the order of execution based on current expectations, and assuming no external funding. In this roadmap we develop the revenue sources according to a bootstrap model, bringing the revenue streams on line in the appropriate order to deploy services and build revenues at a gradually increasing scale.

Table ?? shows the general stages in which we will be deploying services and building revenues. The letter in each cell indicates the stage at which that particular revenue stream will be developed. The revenues will be developed in several stages, consisting of two broad phases, as follows:

  • Phase I: Near-term deployment
    • Stage A. Stage A consists of on-going financing based largely on colocation and consulting revenues.
    • Stage B. Stage B consists of the development of the BySMB/ForSMB revenue model, consisting largely of website development fees, and website hosting fees.
    • Stage C. Stage C consists of the early development of the By<Individual>.net services. The major revenue stream is subscription service fees. There is also a website customization revenue stream at this stage.
  • Phase II: Long-term direction statement
    • Stage D. Stage D consists primarily of development of the advertising revenue stream from the By<Individual>.com services. ByWhere and ByInteraction will also be developed at this stage, providing both advertising revenues and transaction fee revenues.
    • Stage E. Stage E consists primarily of development of the franchising model for all relevant By* family services. At this stage we will also develop the registrar process fee revenue stream. We will also deploy the ByEvent and ByTopic services, and the By* user environments.
    • Stage F. Stage F consists of active development of revenues related to Libre Service Engines, and the WhiteBerry messaging model. In the case of the Libre Service Engines, these consist of software and deployment consulting revenues. In the case of WhiteBerry, these also consist of subscriber service fees, and software licensing fees. Stage F is very flexible in timing.

Phase I is very well-characterized, with a clear execution plan and schedule. The revenue streams are well understood, and the assets are all in place to execute Phase I. The primary emphasis throughout this plan is on execution of Phase I.

Phase II is much less clear. Phase II is more of a long-term direction statement, with no schedule or detailed execution plan.

9.2  Phase I: Near-term deployment

Phase I consists of the revenue development stages to be conducted over the next year or two. This work will take place either under the self-financed model, or based on first-stage financing of up to $2M.

9.2.1  Stage A: Pre-By* revenues

Stage A consists of pre-By* revenues from consulting, and from use of our Data Center for colocation. We are already fully capable of supporting colocation clients, and already have modest recurring revenues from this source. We continue to develop this revenue source by soliciting additional colocation clients.

Table ?? includes a column to show the primary sources of revenues prior to deployment of By*. This pre-By* financing refers to the revenue sources that have financed this initiative so far, and that continue to finance on-going operations.

Thus far the primary sources of pre-By* revenues have been general data communications consulting services, and more recently a small but growing colocation revenue stream. We expect these revenues to be quickly overtaken by the much bigger By* revenue streams. But in the short term these revenue sources continue to play a critical role within the self-financed model. In particular we continue to solicit and populate the Data Center with additional colocation clients as a recurring revenue source.

Though not shown in the table, early BySMB/ForSMB revenues have also been a component of our early self-financing revenues. We have already created BySMB/ForSMB websites for a number of clients, thus generating website development revenues, and also establishing a small but growing hosting revenue stream. We continue to solicit additional BySMB/ForSMB clients.

All the work we have done so far has been financed by the above revenue sources.

9.2.2  Stage B: Deployment of BySMB/ForSMB

The next stage of our execution strategy is early deployment of BySMB/ForSMB. This is the next source of revenue to be actively developed. This is because BySMB/ForSMB clients can be established with minimal additional investment from where we are today, at a small and controllable scale, requiring very little in terms of customer support infrastructure, while still generating significant revenues.

BySMB/ForSMB generates two revenue streams: website development consulting for business clients that require this (non-recurring), and hosting revenues (recurring).

We already have a number of business clients for whom we have created custom websites under the BySMB/ForSMB model. Several of these clients are shown as examples in Table 1. A more complete list is provided on the Neda website at http://www.Neda.com/InternetServices/ClientList. We continue to solicit additional BySMB/ForSMB clients as a source of gradually increasing consulting and hosting revenues.

In addition we are now actively developing the BySMB/ForSMB services to allow self-service (fully automated) creation of BySMB/ForSMB websites by business users. This will allow business clients who do not require custom website development to create their own “standard” website presence on a hosting fee basis.

BySMB/ForSMB revenues will be particularly important in the absence of external financing, because in the case of BySMB/ForSMB, these can be deployed at small scale in self-financed mode. These revenue sources will finance our execution plan in the absence of significant external financing.

The importance of these self-financing revenue streams diminishes depending on the amount of external financing available. With no external financing, these will be very important early revenue sources that we will develop diligently. With a large amount of external financing their importance is greatly diminished in favor of developing the bigger long-term revenue sources.

9.2.3  Stage C: Deployment of By<Individual>.net

Stage C consists of the deployment of the By<Individual>.net services. Under the self-financed schedule this will take place largely in parallel with Stage B. The major revenue streams are subscription fees. There are also website customization revenues for those users who require this.

ByMemory deployment

ByMemory is the first of the By<Individual>services to come on line and begin generating revenues. This is because ByMemory is already largely functional, and ready for immediate account creation and usage by anyone. Also, the support requirements for ByMemory accounts are minimal. Therefore this is an appropriate candidate for immediate revenue development. Development of the ByMemory revenue stream will take place in parallel with that of BySMB/ForSMB. We will initially develop ByMemory at small scale. Though the revenues from this are small, they are recurring revenues, and require almost no customer support.

The majority of the expected revenue stream is straightforward subscription fees. There will also be a modest non-recurring website customization revenue stream for users who require this.

Development of ByMemory revenues consists of the creation and usage of accounts by end users. Our strategy for this is similar to our strategy for populating the ByName service: it consists of identifying and targetting large batches of candidate ByMemory names. We will accomplish this by contacting businesses with access to large numbers of candidate ByMemory names, such as cemeteries and funeral directors. We will offer to create large numbers of ByMemory accounts in batch mode, and advise the surviving relatives that the ByMemory account now exists for their immediate usage. We will also propose entering into appropriate business relationships with such businesses, whereby we create ByMemory accounts for their clients on an on-going basis.

ByName deployment

The next service to undergo deployment and development is ByName. ByName is currently under active development. This is the major Phase I revenue source, and the flagship By* service. It is the most immediately visible of the By* family of services, intended to provide all essential personal computing and communications services for individual users, with extremely large revenue potential.

In contrast to BySMB/ForSMB, ByName services do not generate significant revenues at small scale, and in contrast to ByMemory, ByName services do have significant customer support requirements. Therefore an important element of our execution strategy is to deploy ByName at large scale. Therefore a key element of our execution and revenue-building strategy is rapid population of the ByName service following initial build-out and deployment. Our strategy for accomplishing this is described in the following section.

The ByNumber and ByAlias services have a high degree of functional overlap with ByName; in fact these are largely a functional subset of ByName. These services will generally track ByName in terms of development and deployment

Stage C also includes deployment of the By<Individual>.com services, but as free look-and-see service as an uptake mechanism for By<Individual>.net. The advertising model for By<Individual>.com will not be developed at this stage.

ByName service population strategy

A critical element of our execution strategy is the rapid population of the ByName service with large numbers of candidate users. The key to this is identifying and targetting locations with large batches of potential user names.

In principle, any large database of names will serve for this purpose. In practice it is most appropriate to target the user databases of companies already within the Internet and/or telecommunications sectors. Our initial targets for ByName deployment will be the large ISP companies, wired and wireless. Following that are other companies in the Internet and telecommunications sectors, such as wireless network providers and traditional telephone companies.

We will identify such companies, and present them with our very powerful business message. We will offer to create ByName accounts for all their current users, and advise the users that the account now exists for their immediate usage. By means of this strategy we will create large numbers of user accounts extremely rapidly.

By* deployment consulting

In Section 4.3, and in greater detail in The By* Concept: A Unified Model for Internet Services [11], we describe the very strong business motivations for companies to deploy the ByName service.

Note that regardless of which business model a company adopts for deployment of ByName, it can benefit greatly from consulting assistance from the originators and leaders of the Libre Services and By* initiatives. We have all the necessary experience and assets to assist any company in deploying any By* service quickly and efficiently under any business model.

Therefore there is a further major consulting opportunity and revenue stream available to Neda during early industry adoption of the Libre Services and By* models.

In the long run consulting revenues are rapidly eclipsed by other forms of revenue, since the consulting revenue stream is non-recurring and does not scale. But in the short term this consulting activity plays an important role for a number of reasons:

  1. It is a significant revenue stream, available early in Phase I execution.
  2. In the absence of external financing, it is a major source of self-financing revenues for continuing execution of our plans.
  3. It is part of our strategy for rapid population of the ByName service.
  4. It is part of a broader strategy for facilitating and promoting industry-wide adoption of Libre Services and By*.
  5. In the case of client companies requiring specific features and enhancements, this is a synergistic mechanism for advancing the capabilities and robustness of By*.
  6. Depending on which business model the client company adopts, additional revenues will accrue to Neda based on a business partnership or franchise relationship with the company.
  7. Consulting clients for deployment of By* services may in some cases choose to colocate with us, thus providing a further revenue component.

9.3  Phase II: Long-term direction statement

Phase II consists of revenue development stages to be conducted significantly later. Under the self-financed model these will not be developed until revenues from Phase I operations are sufficient for this. Based on a funding model, Phase II will be financed by the second-stage funding of $15M.

9.3.1  Stage D: Advertising and transaction fees

Stage D consists of major development of the advertising revenue model for By<Individual>.com, and other revenues commonly associated with the delivery of zero-cost services.

Stage D also includes development and deployment of the ByWhere and ByInteraction services, and development of their associated advertising and transaction fee revenues.

9.3.2  Stage E: Franchising

Stage E consists of major development of the franchise revenue model.

Stage E also includes development and deployment of the ByEvent and ByTopic services, and development of the By* user environment.

Stage E also includes development of the processing fee revenue stream from the Neda registrar function.

Under the self-financed model, the ByWhere, ByInteraction, ByEvent and ByTopic services will not be developed and deployed for large scale usage until revenues are available to support this. During Phase I we will continue to do conceptual development of these services, and establish basic placeholder services as appropriate. But these will not be developed as major revenue sources for some time to come.

9.3.3  Stage F: WhiteBerry mobile messaging

Stage F consists primarily of active develoment of the WhiteBerry mobile messaging solution. The WhiteBerry deployment is largely independent of the overall By* deployment execution strategy, so the timing of this is very flexible. This can be played as a wild card whenever industry conditions are right for this.

9.4  Adaptability to financing

As previously noted, because of the multiplicity of business opportunities and revenue streams available, our execution plan is very flexible. In particular the execution plan is readily adaptable and can be modified as appropriate depending on the amount of external financing available.

The above execution roadmap and schedule is a self-financed model, assuming no or modest external financing. Assuming the opposite extreme of a full funding schedule ($2M initially, followed by a $15M second round), we will modify the execution plan in the following ways:

  • We will expedite and accelerate the Phase I execution plan.
  • Rather than executing in a generally serial mode, we will execute in an increased parallel mode, conducting all planned Phase I execution in parallel.
  • We will initiate long-term planning for engineering development of the Phase II technical components.
  • We will also subject the execution plan to a major shift of emphasis, shifting emphasis away from the smaller early-stage revenue sources such as consulting, and instead placing immediate major emphasis on the key Phase I revenue stream of subscriber services fees from large-scale usage of By<Individual>.

    However, emphasis will continue to remain on Phase I. Even under a full-funding scenario, Phase II will remain a long-term direction statement, and no major Phase II activity will take place under the first round of financing. A key goal and milestone to be reached is positive cash-flow status on the basis of the Phase I deployment. This will remain the initial focus even under full financing.

  • We will execute at large scale immediately, rather than building scale over time. In the case of ByName, for example, we will begin to build the technical and business infrastructure to support planet-wide deployment immediately.

In the case of less than full financing, we will expedite the execution plan as appropriate to the amount of financing available. Any funding we receive during Phase I will be used to accelerate the recruiting process and Phase I schedule, and start on Phase II sooner.

9.4.1  Self-financed scenario

Under the self-financed scenario, execution of Phase I will be gradual and controlled. The scale and features of the services deployment will be defined and reevaluated on an on-going basis, and will be reactive and responsive to market conditions and experiences.

The key goal of Phase I under self-financing is to have the Stage B and C deployments become meaningfully operational and generate meaningful revenues. The number of users and the magnitude of revenues required to achieve this goal remain undefined.

In terms of schedule, it is expected that major execution of Phase I will take place throughout 2008 and 2009. As Phase I progresses we expect to see a gradual shift in the revenue balance from Stage A to Stage B, then from Stage B to Stage C.

Under the self-financed scenario there will be no scheduled Phase II activity; the focus will remain on solidification and consolidation of the Phase I deployments. Phase II remains a direction statement, to be revisited later. Without external financing, it is not expected that any Phase II activity will take place until 2009 at the earliest.

All these schedule statements are based on current projections and estimations, and are subject to change based on future contingency.

9.4.2  Fully-financed scenario

Under a fully financed scenario, the focus will remain on Phase I execution. However, all consulting activities will be sharply restricted and highly selective, and will be limited only to consulting projects relating directly to By* uptake.

In the case of the Stage B and Stage C deployments, we will execute in a proactive rather than a reactive mode, defining explicit targets in terms of number of users and revenues, and staffing up accordingly.

With the initial round of financing we will still not conduct any execution of Phase II; the emphasis will remain on Phase I. However we will place some emphasis on scaling up By<Individual>.com usage to large numbers, in preparation for the Phase II advertising model.

The key goal of Phase I under the financed model is to become cash flow positive within the first round of financing. The major use of proceeds is to expedite and accelerate Phase I execution.

The schedule for this remains undefined at this time.

9.5  Promotion

Marketing in the traditional sense is not an explicit part of our plan for promotion of the Libre Services and By* concepts. Note that these are not proprietary products or services, being launched into a traditional competitive industry environment. Rather these are fundamentally different ways of doing things, without peer or precedent.

In particular, these constructs have a set of inherent growth characteristics, as described in Section 4.3. These growth characteristics are based on a set of forces and dynamics including the inherent merits of the services themselves, a growing societal awareness of the merits over time, and the generative and propagative forces of the free software and Libre Services models. These are not unlike the growth characteristics of the World Wide Web, which grew rapidly without any formal marketing at all. Libre Services and By* will grow for similar reasons.

What this means is that marketing in the conventional sense, based on a persuasion dynamic, is neither appropriate nor necessary. Instead what is required is a process of exposure and articulation of the concept across multiple constituencies and communities. Our promotion plan thus consists of three major components aligned with this:

  • Public exposure via widespread distribution of our written materials among all relevant communities
  • Talks and presentations at selected industry forums, user groups, conferences, and academic settings
  • Active participation on the relevant industry mailing lists

We have a comprehensive set of written assets for the promotion of Libre Services and By*. We intend to distribute our articles and use these assets in a variety of creative ways to communicate our message widely within every relevant industry segment and consituency, including the software engineering community, the Internet engineering community, the business community, the investment community, the academic community, our own users, potential business clients and strategic partners, and the media.

These articles and our other written materials will enable us to conduct a strong, coordinated and sustained campaign to promote the Libre Services and By* models at grass-roots level.

In particular we will subject the two key defining documents—Libre Services: A non-proprietary model for delivery of Internet Services [10], and The By* Concept: A Unified Model for Internet Services [11]—to widespread distribution within the technical engineering community. We will do this by distributing these documents on all the relevant mailing lists. We will also target these same documents to key decision makers within the industry.

We expect all of this to generate widespread interest and discussion. The very unconventionality and scale of what we are doing can be expected to generate significant media interest.

9.5.1  Key promotional message

An important consideration is the principal message to be used to promote Libre Services and By*. The principal promotional message will be the ethical superiority of Libre Services as open and free, a communal societal resource, created by society for society. The message to the end user will be the genuine freedoms, privacy, and protection of civil liberties guaranteed by Libre Services. This will be contrasted with the proprietary model, with its fundamental inherent divergence of interests between the providers and the users of the services. This idea will be presented and emphasized consistently in our messages to users and the media.

It should be noted that this is another important respect in which the open and free nature of Libre Services and By* are an asset rather than a liability. The fundamental raisons d’etre for the openness of Libre Services is that this provides a tremendously powerful propagation and growth mechanism, and that this provides a set of critically important engineering, business and societal freedoms and benefits.

But it also provides a unique promotional opportunity. The Libre Services story is genuinely different and unlike anything the industry has seen before, providing a ready-make marketing and promotion engine. People will be interested, people will write about it, and people will discuss it. What this amounts to is free press—the best kind of publicity.

9.6  Recruiting

Execution of this business plan requires the participation of talented and experienced people. We can offer a number of incentives to induce the right people to make a commitment to Neda.

Part of the incentive comes from the inherent uniqueness and interest of what we are doing: we are reinventing the Internet Services industry on the basis of a radically new conceptual model. This is a compelling story, and we expect it to be dramatic and dynamic in the execution.

In addition, we have ample equity available to motivate the participation of potential employees, business partners and investors.

Also, Neda is well-connected within the data communications and Internet community. We have maintained contact with a large pool of talented people who have interacted with Neda throughout our history, either as employees, clients, or business partners. These people have first-hand knowledge of Neda and we of them, so a strong basis for a working relationship exists already.

For these reasons we expect little difficulty in securing the enthusiastic and committed participation of talented personnel. A number of candidates for various technical and management roles have already been identified, and are expected to join Neda when appropriate revenues and/or financing are available.

10  Status and Assets

We have created a complete and coherent set of assets required to move this initiative forward. In this section we describe these assets and the current status of each.

10.1  Conceptual definition

We have done all the necessary intellectual work to create a complete conceptual blueprint for this initiative. We have created the following written assets to articulate the concept and enable participation by others:

  • Libre Services: A non-proprietary model for delivery of Internet Services [10]. This paper provides a complete description of the Libre Services concept.
  • The By* Concept: A Unified Model for Internet Services [11]. This paper provides a complete description of the By* concept and family of services.
  • An Open Business Plan: The By* Family of Libre Services. The Business Plan (this document) provides a complete description of the By* business opportunity.

Together these three documents provide a complete description of all critical elements of this initiative. They are all complete and available in multiple file formats.

10.2  By* services

The following is the current status of all By* services at the time of writing. For the latest status on each service refer directly to the website for that service. All services have placeholder websites in place.

  • Much of the conceptual and architectural design work for the By* family is complete.
  • ByMemory is largely complete, including basic general functionality, and ready for immediate account creation and usage by anyone. It is already populated with a number of active accounts, providing tangible demonstration of the capabilities of the Libre Services and By* concepts.
  • BySMB/ForSMB is sufficiently complete in terms of features and capabilities to support the custom development model of service creation (see Section 8.5, and under this model we have already created BySMB/ForSMB services for a number of clients.

    Creation of the facilities and features to enable the fully automated self-service model is under active development. This is slated for completion next, and is expected to become available in 2008.

  • A complete set of basic ByName features and capabilities have been implemented. These are already adequate for initial deployment of ByName as a live service. The remaining work is the creation of facilities to enable automated account generation. This is under active development, and the ByName service is expected to be deployed in late 2008.
  • ByNumber and ByAlias are largely a functional subset of ByName, and their status generally tracks that of ByName. These are also under active development, and slated for deployment in late 2008.
  • ByWhere, ByEvent, ByTopic remain at concept level only, with no actual functionality implemented.
  • ByInteraction remains at concept level only, with no actual functionality implemented. This will be the last of the By* family to undergo development and become available.
  • The By* user environments remain at concept level only, with no actual functionality implemented.
  • Placeholder websites. All By* services have placeholder websites in place, populated with basic service information.
  • By-Star.net. In addition to the individual By* service websites we have also established a general informational website at:
    http://www.by-star.net

The status of all By* services is summarized in Table ??. The Status column indicates the following status conditions, listed in order of development progression:

  1. Concept only. The service remains at concept level only, with no functionality implemented.
  2. Prototype. Initial design and development is complete, and a prototype services exists for demonstration and proof-of-concept.
  3. Limited usage. The prototype service is in limited usage for validation and testing purposes.
  4. Pre-operational. The service is undergoing active development in readiness for operational deployment.
  5. Operational. The service is fully operational. This means the service is always running, available for immediate usage by anyone, has an installed base of real users, and is generating revenues.

10.3  Software distribution centers

We have established the following software distribution sites to provide the resources required to reproduce the By* services:

  • BySource.org. The distribution center for By* software in source form.
  • ByBinary.org . The distribution center for By* software in binary form.

Both of these websites provide initial basic functionality, and are currently undergoing validation and testing.

10.4  Business infrastructure

The following business assets are in place to support execution of this Business Plan:

  • Processes and discipline. We have established a complete set of engineering and business methodologies, processes and discipline to support our operations. These are more than adequate to support on-going operations and revenue generation.
  • Data Center. The Data Center is state-of-the-art, complete and fully functional.
  • www.neda.com. We have created a very extensive and comprehensive website to support every aspect of our company operations.
  • Equity. Thus far Neda is entirely self-financed and almost entirely employee-owned. Ample equity is available as a vehicle for collaboration, partnership, and employee incentive.

10.5  Execution and revenue status

We have created a complete conceptual blueprint, framework for participation, and execution plan. We have also created sufficient technical and business assets to move forward with Phase I of our execution plan. The initial stages of Phase I have begun, and we are already generating early Phase I revenues. These revenues are small, but they are recurring revenues and growing.

We are now at a point where we are ready to subject this initiative to wide exposure, accommodate participation by others, and begin building increased revenues. From here the next major steps are continued services deployment, widespread promotion of the concept, and revenue-building.

All the basic structures and assets required to execute our plans are in place. We are now ready for immediate, rapid implementation and revenue-building.

11  The Wireless Component

Libre Services and By* include two important wireless components: WhiteBerry mobile messaging, and Libre Community WiFi.

11.1  WhiteBerry mobile messaging

WhiteBerry is an open mobile messaging solution. We initially completed development of the WhiteBerry model in 2001, and documented it fully in the form of a white paper titled Operation WhiteBerry: Creation of a Truly Open Mobile Messaging Solution [9][12].

Though we created a complete conceptual blueprint for deployment and promotion of the WhiteBerry model, we did not subject this article to wide distribution, nor did we execute our implementation plan.

This is because widespread industry implementation of the WhiteBerry solution requires open access to the wireless networks, and in 2001 the wireless network landscape remained very much a walled garden, in which the network providers control and limit network access. Five years later the wireless landscape continues to be a walled garden. It will not be possible for large-scale industry-wide deployment of WhiteBerry to take place until the wireless network access model shifts to an open paradigm.

But WhiteBerry remains fully viable as an open model for mobile messaging, and we believe represents the eventual future of the mobile messaging industry. Sooner or later the closed and fragmented industry of today will give way to an open model allowing general industry-wide interoperability. Whenever the wireless network industry evolves sufficiently to allow this to happen, WhiteBerry is ready to step immediately into its intended role.

In the meantime our own strategic vision has continued to evolve. In 2001 we viewed WhiteBerry as a tactical entry point into the Internet Services market. In 2006 we are now targetting the Internet Services industry directly, and WhiteBerry has been subsumed as just a single functional capability within the By* family.

The Business Plan we wrote in Q4 2001 was WhiteBerry-centric, as an entry point into the Libre Services industry. The current version of the Business Plan is Libre Services-centric, now including WhiteBerry as a single component.

At this point WhiteBerry is a dormant asset, subsumed under the broader By* deployment, and we have no explicit execution plan or schedule for deployment of WhiteBerry. WhiteBerry will be executed as a business opportunity only if this is occasioned by appropriate industry conditions, and the availability of appropriate external financing. Under the self-financed scenario, we do not expect to promote WhiteBerry as a general industry-wide solution.

But it should be noted that WhiteBerry continues to represent a gigantic business opportunity in its own right. For complete details, and for insight into how the 2001 WhiteBerry initiative has evolved into the current Libre Services initiative, refer to the Q4 2001 Business Plan, available at:
http://www.neda.com/StrategicVision/BusinessPlan

11.1.1  WhiteBerry revenues

The final column of Table ?? includes two additional components of the overall By* deployment: deployment of services in non-By* settings (Libre Engines), and deployment of the WhiteBerry mobile messaging solution.

In the context of the By* deployment, WhiteBerry is something of a wild card. It is largely independent of the other By* components, and can be executed at any time, whenever industry conditions are right for this. It also represents a gigantic business opportunity in its own right.

The WhiteBerry business model and revenue streams remain fully valid and viable within the more general By* context. The WhiteBerry revenue streams are discussed in detail in the Q4 2001, WhiteBerry-centric business plan [14]. Here we present a brief summary only. As shown in Table ??, the major revenue opportunities are:

  • Software licensing. We have created a comprehensive set of WhiteBerry software products for all major segments of the mobile messaging industry. All these software products are dual-licensed: they are available as free, open-source software under the GPL (General Public License), and they are also available under Neda commercial licenses for usage in commercial contexts.

    The software licensing revenue stream consists of sales of these commercial licenses into the extremely large mobile messaging market, including ISPs and wireless data carriers, intranet messaging system operators, end-user device manufacturers, systems integrators, and personal desktop messaging users.

  • Software and deployment consulting. There is also a very significant consulting revenue stream associated with WhiteBerry. This consists of providing consulting services to clients who are deploying WhiteBerry throughout the mobile messaging industry. Such clients include device manufacturers, wireless modem manufacturers, wireless network operators, message center operators, and systems integrators. Consulting revenues also include custom software development work for clients who require specific software portations, enhancements or customizations.

    As the architects and developers of the WhiteBerry solution, we are uniquely qualified to provided these services.

  • Value-added service fees. WhiteBerry mobile messaging is provided as a functional component of the BySMB/ForSMB and By<Individual>(except ByMemory) services. This can readily be provided to users as a value-added feature for an additional monthly service charge, thus creating a recurring hosting/subscriber service fee revenue stream.

    In the case of By<Individual>.com, WhiteBerry can be provided as a feature carrying additional advertising exposure, thus creating a recurring advertising revenue stream.

11.1.2  WhiteBerry assets

All resources required to support the WhiteBerry mobile messaging solution are complete and available. These include:

  • Operation WhiteBerry: Creation of a Truly Open Mobile Messaging Solution [9]. This industry white paper provides a complete description of the WhiteBerry solution.
  • MailMeAnywhere.org. MailMeAnywhere is the WhiteBerry software distribution center. MailMeAnywhere also hosts a public forum for the collective development and enhancement of the LEAP protocol engines and integration tools.
  • LeapForum.org. The Leap Forum is the central information and resource center for the LEAP family of protocols.
  • ESRO.org. ESRO.org is a maintenance organization and development forum for the ESRO protocol.
  • EMSD.org. EMSD.org is a maintenance organization and development forum for the EMSD protocol.

All the above websites are fully operational. For complete details see the Q4 2001, WhiteBerry-centric business plan [14].

11.2  Libre Community WiFi

A second wireless component of Libre Services is Libre Community WiFi.

For details about Libre Community WiFi refer to the related project document in the article titled Libre Services: Projects for bootstrapping [8].

12  Competitive Advantages

In the traditional proprietary business model, a key component of sustainable advantage is ownership of assets via intellectual property mechanisms such as patents and copyright. But our business model is entirely non-proprietary, without these formal components of asset ownership. Instead, our competitive advantages are these:

  • Unique leadership role. We are the originators and architects of Libre Services and By*, and we are playing a unique leadership role in their industry-wide promotion and deployment. This leadership role provides Neda with incomparable name recognition status and mindshare within the industry. At the outset, this mindshare will far exceed that of any other Libre Services provider.
  • Conceptual lead time. This initiative is complex and conceptually challenging, but we have a clear and complete big-picture understanding of it in every respect. This amounts to a major conceptual lead time over any potential competitor.
  • Fitness to execute. We are technically and strategically fit to execute this plan. On the technical side we have all the necessary skills, knowledge and experience, and we are fully in tune with the free software culture. On the strategic side we are a small team, internally coherent and fully gelled, with the agility to respond rapidly to changing circumstances and opportunities.
  • Execution synergy. Based on our big-picture understanding we are executing on all fronts necessary to drive this forward. We have thought through every aspect of this initiative, and created a fully coordinated execution blueprint. This creates a powerful synergy among the mutually reinforcing components of our execution plans. Anyone else will at best be doing only a portion of what we are doing.
  • First mover advantage. We have a decisive first mover advantage within what is essentially a new industry.
  • Infrastructure in place. We have built a sophisticated technical and business infrastructure, and have done so with near zero debt. This infrastructure is large, scalable and complete enough to support on-going execution of our plans and rapid increase in revenues. We are already generating small but growing revenues based on this infrastructure.

For all these reasons Neda is uniquely positioned to profit from the By* initiative.

13  Risks and Competition

Despite its large upside, this venture is not without risk. The following is a discussion of the possible associated risk factors.

13.1  Non-risk: engineering execution

On the engineering side, we are fully equipped and capable to execute this plan. We know exactly what to do and how to do it. We have all the understanding and expertise necessary to build all the required engineering components. We also have a complete engineering infrastructure and toolset necessary to move forward with this.

The remaining requirement to move forward rapidly with this is the right engineering personnel to do the engineering work. We are confident we can recruit the right people when revenues and/or financing permit. We are well connected, have many existing professional relationships, and understand the staffing requirements very well. Thus recruiting and execution on the engineering side is extremely well characterized, and a very low risk element of our execution plan.

Note that the technical and infrastructure requirements to becoming an Internet service provider are very demanding. This requires a number of highly specialized skillsets, discipline, and a major initial investment. It requires building major physical assets in the form of a Data Center, and major intellectual assets in the form of processes and discipline. But we have accomplished all of this entirely on the basis of our own in-house abilities, and with near zero debt. We are now fully capable of operating and delivering all By* services at very large scale.

13.2  Major risk: business execution

The fundamental risk associated with this enterprise is inability to execute on the business operations side. The major recruiting and execution risks reside in the areas of management, business development, sales, and operations. Here recruiting and team-building will be significantly more challenging.

The scope of the plan is very large. In the case of a fully-financed scenario, this calls for a rapid growth rate on several fronts. This in turn calls for the creation of a highly sophisticated business structure, and for the management of a rapid and sustained scaling up of operations.

These are standard challenges in the high tech arena, and the business tools and methodologies exist to address them. However, success in this depends upon having the right people for the task. To accomplish our goals, we will need a well-coordinated team of experienced management and business operations personnel.

We have stated that we do not anticipate difficulty in recruiting talented people. But another question is whether we will be able to recruit the necessary people sufficiently quickly to meet our goals. Even with full financing and a skilled core management team, it may not be possible to do the necessary recruiting and team-building fast enough to sustain our growth rate.

However, the severity of this risk is greatly mitigated by the fact that, as the initial proponents of a radical new engineering and business model, time is inherently on our side. Industry conditions are right for the execution of this initiative today, and will remain so for some considerable time. The prevailing industry ideology remains fully rooted in the proprietary services model, and despite anything we might do this will not change for many years.

Thus the window of opportunity for this initiative will remain open for some time to come, and competitive pressure will not come on Neda because of changing industry conditions. Rather, pressure will come on Neda because of competition resulting from our own success. However, this pressure will not arise until our own execution plans are well under way. Therefore we expect to have an ample window of opportunity to do the necessary recruiting and scale up the necessary business structures before serious competitive pressures arise.

13.3  Competing Internet services

There is nothing to prevent another company from competing directly with Neda on the basis of Libre Internet Services. Indeed, it is a defining characteristic of Libre Services that such competition must inevitably arise.

Our sustainable advantages in the face of this competition are those described previously: our leadership role, name recognition, conceptual lead time, execution synergy, first mover advantage, and fitness to move faster and with greater certainty than the competition.

In the long term, it is the first mover advantage that is the most decisive. Since Internet Services is an increasing returns business, the company that first begins to dominate this business will become increasingly dominant as time goes on. But the benefit of the first mover advantage depends on the ability of the first mover to capitalize on it quickly. If the first mover is unable to execute smoothly and rapidly, or otherwise blunders, this advantage can be lost. And there is no other advantage that Neda currently enjoys, that cannot eventually be eroded away by a competing company.

Therefore an inability to execute, coupled with swift, intelligent, aggressive and well-executed competition, can prove fatal to Neda.

13.4  Timing

We have created a blueprint for a transformation of the Internet Services industry into something much more powerful than its incarnation of today. We believe our thinking and vision are well ahead of the industry at large, and it will take time for the prevailing ideas and attitudes of the industry to catch up with us.

This is why we claim that time is on our side, and this is why we believe that we can continue to move forward with our plans on a self-financed basis.

But it must be acknowledged that we could be quite wrong about this, and we could somehow be acting too soon or too late. One could argue that the proprietary services model is too entrenched for any alternative services model to gain any credibility and traction, so for this reason the Libre Services/By* initiative is too late.

On the other hand one could argue that the Libre Services and By* concepts are too far ahead of their time, and societal thinking remains rooted in the mindset and conventions of ownership-based material constructs. From this point of view the Libre Services/By* initiative is too early.

Our response to these conjectures is that we stand by our current assessment. We have a deep understanding of the Internet Services industry, and we continue to pay close attention to its trends and voices. On this basis, we maintain that our assessment of the current status of the industry, and our predictions for its future development, are correct.

While we understand the basis for these conjectures, we believe they are without merit. While the proprietary services model is the prevailing reality today, it is not sacrosanct. It is no more permanent than any other institution, and no less vulnerable to displacement by a more powerful set of ideas.

And while our ideas are radically new and groundbreaking, the necessary precedents and intellectual preparedness exists for them to be understood and taken seriously.

14  The Company

Neda Communications, Inc. is a well-established company with a proven track record of technical proficiency and profitability. Neda was founded in 1991, and between 1991 and 1997 operated as a successful data communications consulting company, with an average income from 1993 to 1997 of over $1 million annually. To date Neda has received no external financing.

Neda has been actively involved in the wireless data industry since 1992. From 1992 through 1994 Neda acted as the lead designer and primary architect of the Cellular Digital Packet Data (CDPD) System Specifications. From 1994 through early 1997, Neda designed and implemented much of AT&T Wireless Services mobile messaging prototype software and systems, for use over Narrowband PCS and CDPD wireless networks.

In 1997, Neda substantially curtailed its consulting activities, and began actively developing the WhiteBerry mobile messaging solution. Between 1997 and 2001, Neda developed a complete set of WhiteBerry assets, as described in the Q4 2001, WhiteBerry-centric business plan.

In 1999 Neda was re-incorporated as a new legal entity, appropriately structured to undergo external financing.

In 2001, Neda made a significant change in strategic focus, shifting from WhiteBerry as a tactical entry point into the Internet Services industry, to a direct strategic targetting of this industry based on the Libre Services and By* initiatives. From 2001 until the present, Neda has created the assets needed to launch these initiatives and profit from their success.

For the past five years our vision and focus has been the creation of the assets required to execute this Business Plan.

We have been involved in the Internet since the very beginning, and consider ourselves long-time students of the medium. As an example of our early vision, note that our Neda domain was registered before that of Microsoft:

$ whois neda.com                 $ whois microsoft.com
Registrant:                      Registrant:
   Neda Communications, Inc.        Microsoft Corporation
   (NEDA-DOM)                       (MICROSOFT-DOM)
3610 164th Place S.E.            One Microsoft Way
Bellevue, WA 98008, US           Redmond, WA 98052, US
Domain Name: NEDA.COM            Domain Name: MICROSOFT.COM
Record Created On 20-Mar-91      Record Created On 02-May-91

We also established the ByName and other By* domains as far back as 1998, long before any of the recent proprietary offerings in this space:

$ whois byname.net
Registrant:
   By Name Services
   C/O Neda Communications, Inc.
   3610 164th Place SE
   Bellevue, WA 98008, US
   Domain Name: BYNAME.NET
   Record created on 21-Aug-1998

We also established our ARIN registration as far back as 1993:

$ whois -h whois.arin.net 198.62.92.0
OrgName:    NEDA COMMUNICATIONS, INC. 
OrgID:      NEDAC
Address:    3610 164th Place SE
City:       BELLEVUE
StateProv:  WA
PostalCode: 98008
Country:    US
NetRange:   198.62.92.0 - 198.62.92.255 
RegDate:    1993-02-23

For complete details about Neda see our website at: www.neda.com

14.1  The people

Neda has a core team of technical and management personnel with extensive experience in the wireless data communications field, and a track record of technical accomplishment and business success. Among the team there are relationships going back almost twenty years, reflecting a long history of productive cooperation. Every member of the team fully understands and is committed to the execution of this business plan.

The team is led by Mohsen Banan, who has been running Neda since 1991. Mohsen was the primary architect of the network structure of the CDPD specification. He is also the intellectual originator and primary architect of the WhiteBerry mobile messaging solution, the Libre Services model, and the By* family of Internet services.

Other team members have a similarly high level of technical and business expertise. Complete biographical data for each team member is available on the Neda website at:
http://www.neda.com/AboutNeda/CompanyProfile/

15  Financing

We have built all this and reached this point on our own, without any external participation or financing. With or without external financing, we will continue to execute our plans. Everything we have built thus far has been accomplished on the basis of on-going consulting and colocation revenues, and we will continue to move forward on this basis. We will continue to develop and deploy the By* services and build the various revenue streams, according to the execution plan described in Section 9.

But this enterprise can benefit tremendously from investment participation. We have created an enormous profit-making opportunity. With the right level of financing we can greatly expedite and accelerate our execution schedule, and take full and immediate advantage of this opportunity.

Our optimal financing schedule for this purpose is $2M initially, followed nine months later by a second financing round of $15M. Under this financing schedule the initial $2M will be used to expedite execution of Phase I. The second round of $15M will be used to execute Phase II immediately on conclusion of Phase I.

But our execution strategy is by nature very flexible. We are currently operating in a self-financed mode, and can continue in this mode indefinitely. However, we can readily expedite our execution schedule according to a wide range of financing amounts and timing. We have all the necessary technical expertise, managerial experience, and business infrastructure required to execute Phase I. But a relatively small amount of financing can accelerate Phase I significantly. Thus we can currently accommodate external financing in any amount from $500k to $2M.

This is an unconventional financing model, but is an appropriate one for this plan. To accommodate this model, we have established a flexible framework for investment participation. This framework allows investors to participate to the extent and timing of their choosing.

The above financing figures and schedule will remain valid until we next update this business plan.

15.1  An open investment model

The By* initiative can benefit greatly from investment, and we have established an appropriate framework for this purpose.

However, we are not following the conventional model for early-stage private investment. The conventional model permits excessive control and exploitation by the venture capital community, to the frequent detriment of the company being invested in. A detailed discussion of the deficiencies of the conventional model, and our reasons for rejecting it, is provided in our Investment Philosophy at:
http://www.neda.com/StrategicVision/Participating/

Instead, we are taking an approach which is open, egalitarian, and permits participation by any interested and qualified investor. Under this open model we are publishing on our website everything necessary for a potential investor to make an initial evaluation of Neda as an investment opportunity. This includes our Open Business Plan and all its supporting documents. Anyone can review these materials and decide for themselves whether to participate or not. A complete description of our Open Investment Model is provided at:
http://www.neda.com/StrategicVision/Participating/

As part of our Open Investment Model we have assembled some resources to assist potential investors in conducting due diligence. These are available on the Neda website at:
http://www.neda.com/StrategicVision/Participating/

15.2  Use of proceeds

Financing proceeds will be used to:

  • Execute a significantly accelerated ramping up of personnel.
  • As described in Section 9.4, expedite and accelerate our execution strategy.
  • Accelerate the execution plan by carrying out development of the various Phase I technical components and revenue streams in parallel, rather than in sequence.
  • Significantly shift emphasis away from the early-stage, lower revenue sources, and towards the later-stage high-revenue sources. For example, development of the advertising revenue model is not something we will do for some time under the boostrap model. If fully funded, however, we will target this for rapid development following the second financing round.
  • Execute a focussed and orchestrated promotion of the By* services.
  • Put in place a highly scalable business structure.

15.3  Financial projections

A conventional Business Plan, based on a bounded product or service, traditionally includes a set of pro forma financial projections. Also traditionally, the projections take the form of a wildly inventive exponential, to be taken seriously by no one.

But these traditions are not right for this Business Plan. First, we are not talking about a product or a service, we are talking about an entire industry. And not just any industry: the Internet Services industry. It’s big, and with or without fictional pro formas, we all know it. Thus the creation of fanciful projections to confirm that, indeed, the By* services have extremely large profit potential is an empty exercise.

And in any case, the actual numerical projections have limited meaning. With or without projections, it is clear that the Internet Services industry and the By* business opportunity are huge, and quantitative projections based on a set of arbitrary assumptions do little to clarify this—they merely present an illusion of clarification.

Also, this entire initiative is about genuine reality, value and integrity. Imaginative financial projections are a form of persuasion. But in this initiative no persuasion, and no spin, is required, and is at odds with the basic spirit of this thing.

Finally, our primary reasons for writing this plan are for the sake of internal clarity and discipline, and to articulate the plan to a broad audience. The standard pro formas are written for a narrow VC (Venture Capital) audience, who expect and demand the jumping of this particular hoop. But the institutional VC audience is just a single constituency among many that form the true audience for this plan. Thus the narrow VC community, along with their expectations, are here marginalized.

When it comes to investment, we are looking for the right kind of investor. Among other things, this means an investor who can quickly grasp what matters and what doesn’t. It means an investor who understands the potential of By* without needing a fictional spreadsheet. In particular, it means an investor who understands that there is a time when financial projections really do matter, and there is a time when they do not. And when they do matter, it means an investor who demands real projections, based on meaningful and defensible assumptions.

When the time is right, we will produce proper financial projections for the right audience.

And in the meantime, we can offer this projection: the profit potential is big.

15.4  ROI and exit

The ROI is expected to be extremely large.

Exit is by any of the conventional mechanisms.

16  An Invitation to Participate

We are doing something big and ambitious: we are reinventing the Internet. In many ways we consider the Internet of today, dramatic though its arrival has been, to have been a false start. Based on what we now know, we are proposing to do the job properly.

But there is what we can do on our own, and there is what we cannot. What we can do is establish a conceptual blueprint for this initiative, and create a starting-point set of assets and services for participation and growth. This we have done. What we can also do is continue to build and deploy the By* services as described in our execution plan. This we will do.

But what we cannot do is make this big. And unless it’s big, it’s not very interesting. But if it is big, then it gets very interesting indeed. But By* can only get big as a result of buy-in and participation by others. Without this, Libre Services and By* will remain no more than interesting historical footnotes in the evolution of the Internet.

Our work so far has been largely conceptual and infrastructural. The next major phase of work consists of growing the By* services into something big and real. And for this we need people, we need business partners, and we need investment.

In creating this opportunity, in building the necessary assets, in establishing a framework for participation, and in documenting everything fully, we have fulfilled our initial responsibilities. We now invite others to join us. We invite and encourage active participation throughout the engineering, business and investment communities.

This is an exciting enterprise, requiring hard work and risk. But the rewards for those who participate, tangible and intangible, will be very great.

References

[1]
" Mohsen BANAN ". " lsip design and implementation notes ". Permanent Libre Published Content "110501", Autonomously Self-Published, "December" 2007. http://www.neda.com/PLPC/110501.
[2]
" Mohsen BANAN ". " the bystar applied model of federations of autonomous libre-halaal services ". Permanent Libre Published Content "180015", Autonomously Self-Published, "August" 2011. http://www.by-star.net/PLPC/180015.
[3]
" Mohsen BANAN ". " the for-profit and non-proprietary quadrant ". Permanent Libre Published Content "120042", Autonomously Self-Published, "July" 2011. mohsen.banan.1.byname.net/120042.
[4]
" Mohsen BANAN ". " sa-20000 home ". Permanent Libre Published Content "120044", Autonomously Self-Published, "September" 2012. http://mohsen.banan.1.byname.net/PLPC/120044.
[5]
" Mohsen BANAN ". "introducing halaal and haraam into globish based on moral philosophy of abstract halaal معرفیِ حلال و حرام به بقیه‌یِ دنیا ". Permanent Libre Published Content "120039", Autonomously Self-Published, "September" 2012. http://mohsen.1.banan.byname.net/120039.
[6]
" Mohsen BANAN ". " libre-halaal internet services defining halaal manner-of-existence of internet application services a non-proprietary model for delivery of internet services ". Permanent Libre Published Content "180045", Autonomously Self-Published, "September" 2013. http://www.by-star.net/PLPC/180045.
[7]
" Mohsen BANAN ". " libre-halaal software defining halaal manner-of-existence of software ". Permanent Libre Published Content "180044", Autonomously Self-Published, "August" 2013. http://www.by-star.net/PLPC/180044.
[8]
Mohsen BANAN " " Andrew Hammoude. " libre services: Projects for bootstrapping ". Permanent Libre Published Content "100103", Autonomously Self-Published, "April" 2006. http://www.freeprotocols.org/PLPC/100103.
[9]
Andrew Hammoude " " Mohsen BANAN. " operation whiteberry creation of a truly open mobile messaging solution ". Permanent Libre Published Content "100006", Autonomously Self-Published, "February" 2001. http://www.freeprotocols.org/PLPC/100006.
[10]
Andrew Hammoude " " Mohsen BANAN. " libre services: A non-proprietary model for delivery of internet services technical version ". Permanent Libre Published Content "100102", Autonomously Self-Published, "April" 2006. http://www.freeprotocols.org/PLPC/100102.
[11]
Andrew Hammoude " " Mohsen BANAN. " the by* concept: A unified model for internet services ". Permanent Libre Published Content "110001", Autonomously Self-Published, "January" 2007. http://www.neda.com/PLPC/110001.
[12]
Andrew Hammoude " " Mohsen BANAN. " the libre services manifesto ". Permanent Libre Published Content "100105", Autonomously Self-Published, "February" 2007. http://www.freeprotocols.org/PLPC/100105.
[13]
Andrew Hammoude " " Mohsen BANAN. " the nature of poly-existentials: Basis for abolishment of the western intellectual property rights regime ". Permanent Libre Published Content "120033", Autonomously Self-Published, "March" 2012. http://mohsen.1.banan.byname.net/PLPC/120033.
[14]
Andrew Hammoude " " Neda Communications, Inc. " q4/2001 neda business plan using a new and powerful wireless messaging protocol to capture the wireless application service provider market leap: An alternative to wap ". Permanent Libre Published Content "110006", Autonomously Self-Published, "October" 2001. www.neda.com/PLPC/110002.
[15]
Inc. " " Neda Communications. " blee and bxgnome: Bystar software-service continuum based convivial user environments ". Permanent Libre Published Content "180004", Autonomously Self-Published, "September" 2012. http://www.persoarabic.org/PLPC/180004.
[16]
Inc. " " Neda Communications. " a strategy for rapidly becoming an internet application service provider joining, adopting and/or licensing bystar a public unsolicited proposal ". Permanent Libre Published Content "180040", Autonomously Self-Published, "August" 2013. http://www.by-star.net/PLPC/180040.
[17]
Inc. " " Neda Communications. " bystar web facilities bystar content production, publication, and distribution services ". Permanent Libre Published Content "180038", Autonomously Self-Published, "May" 2013. http://www.by-star.net/PLPC/180038.
[18]
Inc. " " Neda Communications. " the libre-halaal bystar digital ecosystem an inversion to proprietary internet services model neda communication inc.’s open business plan ". Permanent Libre Published Content "180014", Autonomously Self-Published, "August" 2013. http://www.neda.com/strategicVision/businessPlan.
[19]
Mohsen BANAN Andrew Hammoude " " Neda Communications, Inc. " the by * family of libre services for network service providers: Generic proposal a strategy for rapid entry into the internet application services market a proposal ". Permanent Libre Published Content "110005", Autonomously Self-Published, "September" 2007. http://www.neda.com/PLPC/110005.



This document was translated from LATEX by HEVEA.
Document Actions
Libre/Halaal Internet Services Provided At LibreCenter By Neda

Member of By* Federation Of Autonomous Libre Services

This web site has been created based exclusively on the use of Halaal Software and Halaal Internet Application Services. It is part of the By* Federation of Autonomous Libre Services which in turn are part of the Halaal/Libre By* Digitial Ecosystem which incorporate the following software components: