Pipi Service Model

This document describes a way in which Pipi may be delivered via any means neccessary.

Copyright and Language can be found in RFC1

Change Process

This document is governed by the Consensus-Oriented Specification System (COSS).

Goal

To provide Pipi in one or many forms, with loose-binding, depending on client requirements.

Models

  • Tier 1 - On-premise: Provide Pipi as locally installed, open-source software.
  • Tier 2 - PaaS: Provide Pipi, partially cloud-based.
  • Tier 3 - SaaS: Provide Pipi, fully cloud-based.
  • Tier 4 - IaaS: Provide Pipi, partially cloud-based, with hardware options.