Thanks. I’m aware and recently did it.
3 Likes
What sort of payment plans did you have in mind?
Are you going to go the route of a monthly plan for increased storage, akin to dropbox and google, or were you thinking of a 1 time payment per tiddlywiki?
limits example
- custom name dns “john-com”(paid) → “john tiddlyhost.com” (free)
- storage: 2g(free) → unlimited(paid) or 1TB as google workspace: 1tb, 15GB, unlimited(enterprise) - another limit can refer to the amount of pages maybe something like 100,000 notes like evernote
- plugins
- themes
- support
- contract time and support service
- technical assistance or not
With tiddlywiki not needing a lot of space I think 200mb would be enough for a free plan.
2 Likes
That sounds like a good number, maybe even a tad high for some lighter users, but it’s better to have that extra wiggle room for storage of multiple tiddlers than to not have enough! (and it isn’t like 200mb is an excessive amount!)
I’m currently looking at my folder of every backup I have since first starting my usage of TW and it’s only 102mb! 
3 Likes
Good! Good you may get cash back!
It also, in the modern net environment, makes sense I think?
Since it is a hosting service the models around that may work, for you too, are …
1 - Free — (limited space, no direct support)
2 - Standard — paid (space costed, with support)
3 - Premium — paid & with design (space costed, with support, initial wiki designed & loaded up by a dev you’d partner with???)
Just ideas, TT
Footnote to my last. One issue with TiddlyHost is the server startup performance is not the best in the universe at the moment 
… maybe paid plans could get slightly better performance?
Just a comment
TT
I noticed some comments on “re-direction” … I don’t think that an issue as, as far as I can see, the re-directs would be TO TiddlyHost, not the other way around.
Though it might be worth explaining that to folk who want to use personalised web addressing?
Just a comment, TT
Thanks all - I appreciate the enthusiasm and the ideas being suggested. I’ll add a few notes here in no particular order:
- FYI the mechanism for subscribing (using stripe.com for payments) is mostly complete. I haven’t tried it for real in prod yet, but it seems to be working okay in development mode. I expect there will be some loose ends and details to figure out before it’s 100% ready for launch.
- So, the next steps for me are to figure out what are the distinguishing features between the paid plan and the free plan, and writing the code to make it all happen.
- One feature for the paid plan I’m considering is to have older versions of sites available to be reviewed and restored if desired. This might be convenient if you accidentally delete something you didn’t mean to delete. Tiddlyhost would allow you to roll back to a previous version. There’s still a bunch of work needed to implement that and make it ready for use. Also there’s an impact on storage needed that I need to consider.
- The space allocation distinction is a good suggestion. I’ll first need to implement a way to enforce the storage space limits, so it’s not entirely trivial, but maybe that’s good enough feature for the paid plan to begin with.
- I really like the idea of BYO domain names. I don’t have a clear idea how much work it would take to hook up the DNS and the Letsencrypt, but right now it seems more fun that the “restore previous version” feature. On the other hand, it’s more of a “power user” feature, so less likely to be interesting to the average TH user. (What do you think?). I do want Tiddyhost to remain focussed on the less-tech savvy user, and to be aware that those users are probably under-represented on forums like this one.
- The suggestion about providing a wiki design service is interesting, but for now at least it doesn’t appeal to me much. I think that could be separate from Tiddlyhost. (If someone wants to provide such a service, please go ahead!)
- Re stability and performance, Tiddlyhost hosting is currently low budget to keep costs down, which does impact the stability, but that can change gradually over time, especially if the paid plans become popular. My own tech knowledge of the best ways to host/deploy/manage applications in the cloud is also a factor here.
- Another todo/blocker for launching the paid plans is that I need to write a terms of service and a privacy policy. (I suppose I can find some suitable examples/templates online, but I’m open to suggestions if anyone has experience with this kind of thing.)
- Speaking of legal questions, there’s probably a need eventually to separate “Tiddlyhost the software” from “Tiddlyhost .com the service”. E.g. I don’t think the TH .com logo and my deployment configs for TH .com, should be licensed the same way as the underlying application code. There are plenty of projects out there in a similar situation, so I expect there are good solutions available.
- FYI Tiddlyhost is a weekends and evenings project for me, so progress can be slow and unsteady depending on various factors. That said, I am enjoying it a lot, and I’m optimistic about getting it to realize its full potential. Along those lines, constructive feedback from the community and from Tiddlyhost users is much appreciated and helps with motivation and with figuring out what to focus on next. So, thanks!
-Simon
7 Likes
I had meant to respond before now, to help in your Journey.
- Do consider a tower Hanoi backup rotation to minimise total space needed.
- If only providing to Premium consider giving premium extra space to account for this maintain inside the same quota.
- Perhaps don’t enforce, just Inform and charge more, especially if technically difficult.
- There are different approaches to this but there are
- some minimal ones with little effort on your part and server
- More advanced ones with a Panel interface
- And others with special features and Zone records etc… which you can package and sell as an additional service, with easy to set up options.
- The main thing is to protect your rights and ability to take down stop serving.
- In some ways you are not responsible for content
- Showing you will not use and don’t own others content is essential
- Recognising what ever you or your clients do are subject to law (jurisdiction varies)
“Tiddlyhost the software” from “Tiddlyhost.com the service".
- I am interested in setting up a similar server, not in direct competition, but for other services. So yes please differentiate.
- ideally open source solution with purchasable services and support
I have a suggestion: maybe paid users could host non-tiddlywiki files in their tiddlyhost “folder” ? This would make things like setting up a RSS feed much easier (see https://talk.tiddlywiki.org/t/new-tiddlywiki-newsletter-beta-work-in-progress) since a GitHub account wouldn’t be needed.
2 Likes
And like wise static tiddlers and landing pages for more Search Engine Optimisation (SEO) juice.
- however this could add complexity to achieve this, with a file dashboard etc… but I expect there are Open Source solutions out there.
This would play nicely with image hosting if it’s possible to follow through on saq’s uploader:
-Springer
Hello! Does TiddlyHost charge based on the number of wikis, or are these just technical limitations and not commercial ones? The same goes for the size of the wiki and embedded media? Because I can’t pay online. I don’t have that right.
Of course you can continue to use tiddlyhost as a free service!
The paid plans offer more features (such as a history of backups, which is fantastic for peace of mind and problem-solving), but the site is generous with allowing free accounts to develop multiple sites, and I don’t believe there’s a size limitation on the wikis hosted there.
(Of course @simon might have to change those policies if storage demands from free accounts become unreasonable. Right now, it’s a really great support for the community since people can easily explore the web hosting convenience while evaluating TiddlyWiki.)
1 Like
My goal was to create a TiddlyWiki via Firefox bookmark. TiddlyHost isn’t ideal for this kind of thing (I asked ChatGPT to translate your words because I’m autistic, and it said that if I did that, Simon would switch me to a paid plan, but I’m not allowed to pay online), I don’t see any other hosting method. I would like to use my TiddlyWiki system as a database where each wiki is hosted in a bookmark, because I want to use TiddlyWiki as my second brain to record all my research and logs, because yes, I am curious, eager to dissect every piece of information.
What I’d like to do is:
1 TiddlyWiki = 1 Firefox bookmark.
That sounds excessive as a typical link is less that 128bytes, and one Tiddlywiki is at least 2.5Mb in size. And yes you can use tiddlyhost for free but if you create thousands of wikis it would be abuse.
What do you want to do that?
Perhaps their is a better approach
- One tiddler per bookmark in the thousands inside one wiki makes a lot more sense.
All I’d like to do is create a huge wiki library, so I think TiddlyHost might not be the best approach for that. I suggest we continue this discussion in my thread.