"We spend the time and energy searching all over the web for cheaper reservations for you", are you really spending time on searching things manually? If so, I wouldn't pay anything for such a service, because you may apparently go on holiday and don't care about my reservation. If all is automatic, then I could go for it. However, then "spending time and energy" is a lie.
I believe anyone should be able to submit their reservation, along with credit card details. If you do find the cheaper rate somewhere, you charge them at that point and present with the offer.
I found the reason to visit Stackshare real quick. I just checked today's Analytics of my startup https://www.virtkick.io - 20% visits originates from stackshare, so I now have to claim it. ;) Quite funny, I tell ya.
It doesn't change the main concern, though. leanstack.io was the greatest site to find services.
Leanstack.io was extremely useful for discovering services. Needed best A/B testing tools? I used to go to Leanstack. I don't seem to find any reason to visit Stackshare. I don't really care whether Twitter uses Zendesk or Freshdesk.
You may be surprised that VirtKick wraps WebVirtMgr and uses it as a JSON API for libvirt. :-) This is a temporary solution but does the job - it allowed us to start real quick with features that users care about, instead of harnessing libvirt. (Of course, SSH key injection is in a scope of our project! https://github.com/virtkick/virtkick/issues/6)
I'm sorry but we missed your comment. Just created an issue to track this problem: https://github.com/virtkick/virtkick/issues/65 Please subscribe to the issue so you'll get the updates.
Frankly, there are two mutually exclusive camps: free software and open source. I myself sympathize with free software (GPL) whereas RushPL with open source (MIT). Selling proprietary versions has never been the reason for CLA, though! We want to be able to re-release VirtKick under MIT (and automatically get rid of CLA) if we get funded, so businesses have no problems with it. (See https://news.ycombinator.com/item?id=8527999)
What one regards as a feature, other regard as misfeatures. If you like virt-manager, then VirtKick isn't really for you. We value a simple UI more than virt-manager, and REST API more than virsh. We don't say your way is wrong. It's just more difficult.
Existing libvirt clients, at least those that we know of, aren't super reliable though. libvirt stucks when there's too much happening on the HV, or denies jobs without even trying (e.g. when a pool has async jobs). A backend that schedules tasks for background execution is needed for that (and we have it), so even now we're not "just" a frontend for libvirt.
The use case is a very simple panel with zero virt knowledge needed to start.
Yep. Our 128 GB hypervisor wasn't enough. We redirected traffic to a static HTML prototype, so - at least - you guys have a chance to see the design and planned features. https://demo.virtkick.io/
Thanks for your comment. UI comes first as every user will hit it. API comes next. We planned DigitalOcean-compatible API altogether with a CLI. Looks like we removed this from our website by mistake (will get it back real quick), but it's listed in our IGG campaign: https://www.indiegogo.com/projects/virtkick-take-cloud-back