2016/7/9更新
經營不到一年的Kloudsec將於8/1關閉，主要問題在於公司沒有從Kloudsec獲得收益，
建議用戶遷移到CloudFlare等支持SSL的CDN服務。
Kloudsec官網 https://kloudsec.com
![](data:image/svg+xml;charset=utf-8,<svg height="582" width="1312" xmlns="http://www.w3.org/2000/svg" version="1.1"/>)
信件全文：
Hi all,
It is with great sadness that I have to inform you that Kloudsec is shutting down.
Why is Kloudsec shutting down?
1. We have been funding Kloudsec out of our own pocket
2. Kloudsec is very expensive to maintain (upwards to $10000 / month)
3. We are unable to make money from Kloudsec, nor raise any funds for it
We will shut Kloudsec down on 1st August
From now till then, we will not be maintaining the service.
Migrating out of Kloudsec
Migrating out of Kloudsec is extremely simple. All you have to do is to point your domain back at its origin server.
You will lose the HTTPS cert. But you can fix that by
* either issuing your own LetsEncrypt certificate
* or using Cloudflare.
Lessons learnt
From the start, we are extremely lucky to have a small revenue stream that let us to experiment with cool products. And Kloudsec is one of our biggest experiment.
There are a couple of things we did right, and a couple we did wrong.
We did right by having the right team come together, building a seriously sophiscated product. (Thank you Ivan and Bach)
We did wrong by building a sophiscated product that made it hard for a small team to maintain, let alone scale.
We did wrong by building a product that was not immediately useful enough so much so that people will pay for.
We did wrong by building a product that was too expensive to maintain.
We did wrong by assuming that traction solves all ailments. Not in Singapore, you don’t. There is no good venture money for real hard-tech software startups in Singapore.
We did right with pulling the plug so we can learn from these mistakes and work on the next product.
What’s next for us
From Kloudsec, we identified a few niche problems that we will be looking to solve. In other words, we will continually be building.
And you can be sure from our next product onwards, we will charge right from day 1 so we can sustain the product financially.
Lastly, thank you!
Thank you. Most of you have spoken to me, or read the posts I’ve written on Github, on Hacker News, or Producthunt about Kloudsec. You guys took a leap of faith in trusting this small unknown team and product, and used us.
I’m sorry to disappoint you with this piece of news, but I’ll try better next time.
If you like, you can follow me on Twitter at @nubela. You can also contact me at anytime at steven@nubela.co
Steven Goh.
Kloudsec是今年才推出的CDN服務，
與KeyCDN一樣使用Softlayer伺服器資源建設節點，
目前節點包括英國、美國、新加坡，
與CloudFlare一樣使用Anycast所有節點IP相同，
不須修改網域NS紀錄就可以使用CDN，
並且免費提供SSL憑證安裝或搭配Let’s Encrypt簽發功能，
補足Incapsula免費版無法使用SSL的麻煩。
在官網按下preview dashboard申請服務。
輸入要設定CDN的域名。
進入Kloudsec控制面板，請先驗證DNS配置。
分別修改指定A記錄到Kloudsec提供的IP，完成後按下驗證。
(剛開始可能會驗證失敗，不用重新設定，系統將會在DNS生效後自動完成驗證)
Speed頁面可以打開頁面優化。
Kloudsec在這裡提供頁面優化的等級說明，通常選Basic等級即可。
Reliability可以設定離線緩存頁面。
選擇免費方案的離線緩存(只有單頁面緩存)。
完成離線緩存配置(因為只有單頁面，站點當機時幫助有限)。
Protection頁面可以啟動網域Let’s Encrypt簽發功能。
開始簽發網域(可能需要等待一段時間才會完成)。
點選左邊面板的網域，設定網域的SSL配置。
包括自動重新導向HTTPS、自動重寫內容到HTTPS、使用HTTPS(443)訪問源站等功能。
至於Web Shield功能尚未成熟，不建議使用。
站點配置可以修改源站IP或CNAME。
Kloudsec很適合搭配新版360網站衛士做為海外CDN，
讓網站在海內外都能透過近端CDN節點快取提高訪問性能。