Proposed Payment Model

The following are details of the proposed payment plans for Codaset. These are not final, and are subject to change.

To leave your feedback and comments, please jump into the #codaset IRC channel on irc.freenode.net, or email Joel directly at joel@codaset.com.

Pay as you Go?

My favoured model is a a "pay as you go" or amazon web services style service. Meaning you would pay a per project fee. For example, we could charge $1 per project, and each project would include 1GB of space. So if you had 20 projects, you would pay $20 per month, and would have 20GB of space. The space would be shared across all your projects, so one or more of your projects could use 10GB of your 20GB total as an example, and the rest of your projects would use the remainder of the space in any way you want.

• The first private project would be free, and all public projects will still be free.
• Public projects would use and share your private repo space.
• A minimum of $5 per month or something similar will have to be incurred. So if you want more than one private project, you would then pay $5 which will give you 5 private projects. Each new project thereafter would cost an additional $1 each.

Enterprise/Company Pay as you Go

If we go with the "pay as you go" model, what about forking private projects? I am aware that some companies use the forking methodology to distribute development of a project between members of a team. So each developer may end up with their own fork of a private project. This could get a little expensive if we charge per project.

So an idea would be to introduce an enterprise plan, that would run along side the normal "pay as you go" plan. This enterprise plan would allow the creation of enterprise or company accounts. A company account would be similar to a regular user account, but would act as a kind of umbrella for several user accounts. So within a company account, you can then assign several regular user accounts.

As well as adding benefits in managing users of a company, this could then be used to manage forks within a company account. So a company would still pay the same price for private projects, but would then pay a monthly premium to allow members of that company to create as many forks that they wish of that project.

In this case, a fork would be a repo-only fork. Meaning that the fork will not include any other features other than the source code management. If you want a fork to include the usual project features of ticket management, blog and wiki, then the usual per project fee will be incurred.

Company Accounts

Let's define what a company account can or cannot do.

• Anyone can create a company account.
• You can assign any number of existing or new projects to a company.
• A set monthly premium will be charged per company account.
• You can create as many private repo-only forks (see below) of a company project as you wish.

Repo-only Forking

Under the "pay as you go" pricing model, each private project will incur a monthly cost. This will also apply to project forks. But sometimes you may only want to fork the repository only, and not bother with tickets, wiki or a blog for your fork. So you can therefore fork only the repo.

• Repo-only forking for private projects will only be available with a company account.
• Repo-only forking will also be introduced for public projects, which as with any other public project, will incur no cost.