Between the several small details that need to be taken care of, we needed to set up a user authentication system.

I think that the UserLand subscriptions based model is just perfect for this kind of software (for almost any kind of software, actually), because:

• We get a steady revenue stream
• Users get updates
• We only have to maintain and support one version of our code: the latest.

So we have developed an architecture to be able to easily manage our updating process and after discussing the issue with a few fellow tools developers, we decided that we'll make this system available to all developers that will want to join us.

Here's how it will work:

The whole system will be based on two servers: one to manage subscriptions, the other one to serve the actual updates.

As soon as we'll be ready we'll release the client side part, and any developer will be able to include it in its tools and link it to the code.

Just setting a few flags tool-side, the developer will be able to determine the kind of limitations that he'll want to impose to the user, for example: a non registered tool might simply not work, or it could work for some days.

Then he or she will have to register with the server and upload the tool to the updates server. From this point on each update will be verified against a serial number: no valid serial number, no update. Just like all UserLand software.

Some other details:

• Each developer will have his/her own personalized registration page, with company logo and all forms will be personalized
• All sites will be operated from the xml-rpc.it domain name
• All developers will be able to access to their customers' data on a secure connection
• The system is build as a registration infrastructure, so it's intented also for tools that will be distributed freely but will require a registration
• Of course we are also implementing a payement gateway for our own software. We'll probably be able to provide this service also to other developers, they'll be able to access the registration system via xml-rpc

Why we are doing this

Because what we'll get is a larger userbase, and we'll be able to build on this base much better if we work together than if all of us work on his own system.

Currently we don't plan to charge anybody for this infrastructure, but we might decide to change this at some time. Of course, any developer can leave at any time bringing his user list away.

We'll probably have the first version of this system ready sometime this week, stay tuned, if you are interested, click here: .