Appiyo on cloud

  • Any individual can independently become a member.
  • A group of individuals can decide to form a collaborative team. Every individual must be an independent Appiyo member first. A representative of the group can then create a Group in Appiyo and invite others to join the group.
  • A company interested in using Appiyo must create zones. Zone owners can invite other members into their zones. During the evaluation stage, it would be advisable for a primary group of individuals in the company to first become members and experience Appiyo. They may subsequently choose to co-opt other co-employees also, by inviting them to become Appiyo members.


  • Zones are of two types. One is a ‘community zone (My Zone)’ and the other is a ‘commercial zone’.
  • Community zones are lifetime free. They may also receive ads.
  • Community zones should not be used for commercial purpose.
  • Dormant community zones will be quarantined. A dormancy of more than 3 months will be reviewed and quarantined after alerting the zone administrator.
  • Commercial zones will be charged. Refer Appiyo Pricing.
  • Adapters and End-Points will be priced separately and will be specific to a need.

Zone Allocation

  • On sign-up, every member gets her/his own exclusive community zone. Every member can have a personal & unique experience in her/his exclusive community zone.
  • When a member wants to go commercial with her/his solutions, they have to opt for commercial zones. These zones will be ad-free.
    • Example A, a BPM training company can opt for a commercial zone, create different groups (Batches) inside the zone and invite trainees into those batches for the duration of the program and close the batch upon program completion.
    • Example B, a company is interested in a solution created by an Appiyo member. The company should create a commercial zone and the solution will be deployed into that zone.
  • By default, the primary member of a zone will have administrator privilege which will allow the member to operate her/his zone the way she/he wants.


  • A container is computing resource (virtualized OS).
  • A community zone will be powered and limited by a 32MB container.
  • A commercial zone will be powered by a 256MB container or multiples of it. It can scale with need.

Appiyo Pricing (subject to change)

  • A container unit (256MB) inside a commercial zone will be charged at $30/month. Additional containers of 256MB can be purchased with need.
  • Price of adapter and end-point will be specific to need. Discussions will be necessary for price determination.
  • If a member/group wants to move a solution (processapp) created by member/group into Appiyo processtore (marketplace) with an intent to monetize it, there may be a onetime quality check fee of $250/processapp/check-in. This quality check becomes necessary to ensure that there will be no detrimental effects on the Appiyo platform environment due to faults.

How will I pay for containers in commercial zone?

We plan to integrate with payment gateways soon. Until then, we will provide bank account details into which money has to be credited electronically. Payment will be quarterly in advance.

Appiyo on Private Deployment

  • This will be case specific and will be decided by Appiyo.
  • Private deployments will be independent of Appiyo cloud model and either of the two models will not have any bearing on the other.
  • The model will be based on a onetime license fee ($10,000 per socket) and 22% AMC/year for 3 years.
  • Appiyo will prefer partners to offer their services or the customer to self- serve.
  • Appiyo will share license and AMC revenues with partners who enable private Appiyo deployments.

Appiyo as a mobile app

Appiyo can soon be downloaded as a mobile app from Google playstore and later from Apple istore. Until then, Appiyo can still be accessed using mobile browser.


When Appiyo is downloaded into a mobile, the device is connected to the Appiyo platform, thus enabling notifications. Notifications to non-members will have to be routed through a mobile SMS gateway using an appropriate SMS plan. This will have to be provisioned separately.
In an on-premise installation, the mobile must have access to the Net for notifications to work.


The preferred architecture is to have the database collocated in the cloud where Appiyo is operating. This will eliminate bandwidth consumption and also latency issues. Currently supported databases are MYSQL, MS SQL and Postgress. In the future, more databases will be supported. Appiyo plans to have strategic partnerships with cloud db vendors and cloud service providers in the future. This will create more choices for customers.


The workflows modelled are interpreted and executed by Appiyo’s BPM engine. Javascripting will enable additional processing logic. This will be extended to include other scripting langauges like Python and nodejs.


Currently Appiyo provides adapters to Salesforce, OpenERP, Alfresco, Facebook, Twitter, SMTP mail server and Web Services. REST APIs will be included soon. Appiyo plans to include more adapters progressively. Unique adapters and end-point connectors will have to be custom built by Appiyo.


Port-tunneling with required permissions will allow Appiyo to connect to end-points / datasources which reside behind firewalls. Alternately, an Appiyo listener can be installed behind the firewalls and can serve as a proxy between external Appiyo and internal datasources. The latter is presently unavailable and is included in the Appiyo roadmap for next release.

IP and device based access security in Appiyo?

To enhance security while accessing Appiyo zones, IP range and device id based security features will be soon implemented in Appiyo. This will prevent unauthorized access.


Every Appiyo member is an owner of his/her community zone. Likewise a creator of a commercial zone will be the zone owner for that zone. Zone owners are de facto zone administrators who can operate their zones and assign privileges to zone members.

Date & Time

Date & Time stamps are important parameters for information about discussions and processes. Currently, Appiyo uses GMT of server and converts it to client (browser) time. Later, we plan to introduce preferred time zone in the user profile giving user a preference setting option.


How do I make use of an app built by somebody and which is of interest to me?

Currently apps are restricted to operate in the zone in which they are created. In the future release, Appiyo will give import-export feature to enable movement of apps across zones. Marketplace will also become available in the future release from where apps can be sourced.

How will I know about apps built by others and which are available?

From the Marketplace (not available yet). Also, by using ‘explore’ option in ‘Applications’ menu.

Can I build stand-alone apps?

Apps built in Appiyo will only run inside the Appiyo environment.

Can apps built in Appiyo be plugged into another external app?

Yes, by invoking REST APIs to call workflows inside Appiyo. Custom UIs may have to be built separately outside Appiyo in such cases.

What happens if my container capacity is exceeded in My Zone (community zone)?

The zone administrator will have to decide what processapps have to be de-prioritized and un-deploy them to release container capacity. Or, the zone administrator can opt for a commercial zone.

What happens when my container frequently exceeds capacity?

This will happen if a workflow is improperly designed. Example, infinite loops can be a cause. If a zone container exceeds memory because of such reasons, the container will automatically get re-started. However, if the occurrence exceeds 10 times, then the zone will be blocked for audit. The zone administrator will have to get in touch with Appiyo support team.

What will limit container capacity in My Zone (community zone)?

Both deployment and execution of processapps will utilize container capacity more than the social component. The zone administrator will have to manage container capacity utilization in My Zone and opt for a commercial zone for processapps, if scale becomes necessary.

Is there a storage limit for transaction data in My zone?

Data in Appiyo comprises many types. They are social related data such as discussions, photos, documents, etc., Process related data such as process instance information and apps related data (record data). There will be a 10 GB limit enforced on the volume of all data.