Kitely pay-as-you-play changes


i *think* i’m properly grasping Kitely’s new pricing policies but since they won’t be fully revealed until the first of the year, there’s still a little mystery in what they will be. i think if Kitely had done this from day one, there wouldn’t be such confusion

Kitely’s new pricing is still a heck of a deal and i have to keep reminding myself of what our past was. first there was SL and at $1000 setup and $295 a month for 15,000 prims, that is an extremely expensive offering. with SimHost, we paid $159 for 16 regions and an unknown max number of prims (it felt like 40,000 prims would have allowed about 40 avatars online)

chuchu2but . . . Kitely set their own yardstick and a shift from that causes concern

so much so that we have truly placed Enclave Harbour on the back burner. it was a slow go anyway and taking longer than we both thought, but now it is not an active project and won’t be until subQuark’s ChuChu Chicken & Pedro the Goat first series of books are published. that project has a timeline putting it at being published in May. along with that comes an effort to promote it, so neither of us will be back to work on Enclave Harbour until the summer

had their not been this “upheaval”, Enclave Harbour would continue to be poked at and slowly move forward (very slowly). there have been a couple of incredibly generous offers to host Enclave Harbour for free and for incredibly low-cost and we’ve also thought about doing it free on SoaS. the disadvantage of SoaS is that only Windows peeps could do it and there’s a significant technical hump to overcome

it’s funny how a shift like this can have profound effects

stepping back from our initial reaction, Enclave Harbour could move ahead and be done for $55 a month via Kitely ($35 for our Gold plan and $20 a month for 100 workbook user-hours). that’s a lot cheaper than SimHost would have been and has all the benefits of Kitely doing the accounts

but, we have changed priorities and Enclave Harbour is on hold until the summer but we probably will be keeping the Kitely $35 Gold plan (30 sims is amazing and i think would still be 100,000 prims per world – so Enclave Harbour’s 16 sims is 100k but so is the one sim Hax Nuit – i could add a 9 sim 100K EnerGoober world if so inclined)

we will see where things shake out and one of my fave grids may end up with the Ener freebie store in January (or it’s contents) and maybe even Hax Nuit!

i’ll be changing the access to our Kitely public worlds and removing the space base and cool ice campus – currently we pay the minutes, but starting thursday, visitors will be charged 1KC per minute and i’ll be interested to see how that impacts our history

OpenSim – ever changing and, overall, that’s a good thing! =)


ChuChu Chicken! =)

Twitter Tumblr Digg Reddit Stumbleupon Delicious Facebook Plusone Pinterest Linkedin Tumblr Posterous Snailmail

written by Ener Hax

December 23rd, 2013 at 9:44 am

3 comments to 'Kitely pay-as-you-play changes'

subscribe to comments with RSS or trackBack to 'Kitely pay-as-you-play changes'.

  1. Hi Ener :-)

    Just to answer your question:

    Yes, Metered worlds will continue to support up to 100,000 prims per world.

    Ilan Tochner

    23 Dec 13 at 7:11 pm

  2. I’m slightly confused by this post. I thought all open access worlds had to meet the cost of visitors from 1st January, although the cost is factored in for unmetered worlds?

    Anyway, love the illustrations and thanks for your support for Kitely and SoaS through 2013. Have a great festive season and best wishes for 2014.

    Graham Mills

    24 Dec 13 at 12:48 am

  3. Hi Graham,

    You are correct. Starting next year the world manager will always be the one paying for visits to his or her world. Either a fixed-price per month or using a pay-per-use (time-based) billing option.

    Ilan Tochner

    24 Dec 13 at 7:02 am

leave a reply - add your thoughts

you can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>