Skip to content

Find out how moving to Kinsta could save you $2,400+ a year on site costs.

Speee将内部CMS切换到Kinsta托管的WordPress,以降低成本并简化操作

The Speee name below its logo, a blue circle bisected into two slightly disjointed halves.

“解开一切,为我们带来未来。”这就是 Speee公司,一家总部位于东京的数字转型(DX)公司,致力于业务发展中的数据驱动链接。Speee现在正在广泛扩展其业务活动,如房地产销售和评估服务 Ie Uru公司 以及他们的家居装修公司介绍服务 努里凯,以及其他各种营销DX业务。

快照

  • 行业:数字化转型(营销和房地产)
  • 员工人数:约400人(截至2022年1月)

问题所在

Speee开始运营内部开发的CMS,但他们在三个方面遇到了问题:成本、可用性和稳定性。

2018年,我们为内容创作和文章管理开发了一个内部无头CMS。然而,当我们真正开始操作系统时,我们发现了几个问题,这导致我们考虑更换它。当时有三个问题。

第一个问题是开发和运营成本的增加。

It costs a lot to develop and operate a CMS in-house. However, since its scope is limited to internal usage within the company, a large return cannot be expected. That inevitability makes it difficult to invest in development and operation.

The second issue was usability.

Even though it was a CMS for internal use, it was essential to have an easy-to-use system in order to rapidly create high-quality content. Yet we lacked strong investment in development after the initial release due to high costs and low return on investment, as mentioned above.

As a result, no system improvements were made after the initial release, and content creators continued to use a very inconvenient UI and infrastructure. Without a doubt, that in turn led to lower-quality content.

Finally, the third issue was that the old CMS became a factor that reduced the stability of our other systems.

Since the CMS we developed in-house was a headless CMS, the actual content display was done by another web application. This web application needed to call the API of the headless CMS, but when this API went down, the entire web application would often go down as collateral damage.

Speee's business R&D listed out in three steps.
Speee’s business R&D.

The Solution

Time for drastic measures to put an end to snowballing costs. The team looked toward a SaaS solution, with Kinsta rising to the top of of possible candidates.

Increased development costs had become a bottleneck, and so we decided to move to SaaS. The question was which SaaS to move to. From our research, we narrowed it down to a couple of candidates, including Kinsta, and there were three great things about Kinsta in particular that we focused on.

First, on Kinsta we can use WordPress, the most popular CMS in the world.

We already had a department in our company that was using WordPress, so we had some familiarity with it. Also, since many people use it for a wide variety of purposes, we recognized that its functionality and scalability are very appealing.

Second, Kinsta’s managed service has a broad reach.

Although it’s easy to get started with WordPress, it’s a headache to keep PHP and WordPress properly up to date. With Kinsta, PHP and WordPress updates can be done with just a few clicks, and CDN and domain management can be done from the UI. These were features we were looking for, as we wanted to focus on content creation and service development.

Third, Kinsta’s price is reasonable for the features.

With all of Kinsta’s rich managed features mentioned above, the price is relatively low compared to the services we were considering.

We chose Kinsta because of its superiority on the above three points in comparison to the competition.

The Result

With the combination of WordPress and Kinsta, their workflow became incredibly smooth. Plus, system stability improved immediately.

First of all, thanks to the switch from our own CMS to WordPress, we are now able to create high-quality content faster. This is thanks in large part to Kinsta’s high-quality UI and system design, as well as the assistance provided by its wide variety of powerful features.

In addition, since WordPress is so widely used, many content creators already have experience using it in the past. Even if they run into problems, solutions are readily available online, which reduces the cost of exposition and research.

The most remarkable thing for us is the stability of Kinsta’s system. Before we moved to Kinsta, every year we had several malfunctions that affected our users, but since migrating to Kinsta, those problems have completely disappeared. This is not only because Kinsta itself is highly stable, but also because the probability of failure has been reduced because we no longer need to link multiple systems through an API.

另一个原因是中间件和插件现在保持适当更新。在过去我们的专有CMS中,中间件和库的更新往往被忽视。现在,我们使用Kinsta的函数升级PHP和WordPress版本,并通过半自动维护CI/CD创建了一种自动插件更新机制。

Kinsta是员工限制的解决方案;未来校对是关键。

与室内建筑或IaaS相比,Kinsta提供的WordPress体验是 相同或更好的质量成本的分数或更少 -不仅对于初始构建,而且对于 正在进行的操作. 无论如何,你自己试试吧。
Tarun Gehani
西田和文先生数字转型事业部开发平台组长
斯佩伊。日本

准备好开始了吗?数百家组织使用我们的基础设施来扩展其业务,包括高流量博客、初创公司、机构、大学和财富500强公司。我们希望你能加入我们。 查看我们的计划

Like what you see? Join Kinsta!

Check out our plans from starter level to enterprise solutions. Find what fits you, or contact us if you need something special!

See Plans Contact us