＜Background＞
There are a number of services that are only available in the cloud that allow you to build and mock up low-code, business-specific web applications in an instant.
Although they are not well known, Zoho Creator and Amazon Hanycode (including RunMyProcess) are all unique, and only Zoho Creator seems to be flexible.
Zoho Creator is the only one that seems to be flexible. However, in Japan, the market share is low and Kintone is famous. And it doesn't support Japanese.
The goal is to create a PHP-based tool that is simpler than Zoho Creator, more flexible than RMP, and uses a homegrown GUI-based MVC development model that can be used for both non-coding and low-coding.
We aim to create a PHP-based tool.
In addition to the above, we aim to expand our product line to include services specialized in logistics, finance, and healthcare, utilizing the business knowledge we have cultivated at Simpo, as well as integration with various cloud services.
We hope to make progress in the Japanese market and eventually in the global market.
＜Sales model＞
Normally, each cloud container is provided under a subscription contract, and the maintenance support for the infrastructure part is not required.
Based on this, I have considered the following
1. Build and provide AWS IaaS EC2 for each customer, and charge the actual amount spent on usage (pay-as-you-go sihmpo expenses) + basic fee (shimpo sales)
Sell the entire cloud environment to customers who do not want to maintain every detail.
The infrastructure itself is guaranteed by AWS, so Shimpo is not responsible for it.
System maintenance is done by Simpos, and since it is a subscription service, if the customer requests an upgrade of the core engine, it is done. In that case, we have to make sure that existing applications owned by the customer are not affected.
2. AWS will be contracted as a whole service provided by Shinpo, and will be strengthened and enhanced according to the number of customers.
Internally, containers will be provided on a subscription basis for each customer.
AWS guarantees a certain level of infrastructure, but maintenance of the infrastructure part on AWS and system maintenance are required.
The rest is the same as "1."
3. Deploy as in "1." or "3.", but provide custom build and support on the customer's on-premise (but with sub-functions provided from Simpo's cloud) or customer-owned cloud.
Custom build and support on the customer's on-premise (but with sub-functions provided from the Simpos cloud) or on the customer's cloud.
This is required when the customer owns the infrastructure resources.
In this case, the customer will receive a monthly fee for initial implementation support (labor cost), a license (buyout) fee, and a monthly subscription fee for sub-functions.
Maintenance is optional.
＜Assumed environment＞
VM environment (EC2/GCP)
Linux (CentOS/Ubuntu)/Windows
PHP 8.0.7
Postgresql v13
JS-OSS: jQuery UI/jQuery/Tabulator
Apache2 (HTTPS)
Note: Laravel is a comprehensive framework that can handle MVC model development at the CUI level, but it is slow and runs on many modules (Node.js/npm/composer Artisan command tools, etc.).
Therefore, we would like to make it a GUI-based MVC model development tool that can take the place of Laravel, assuming that it is developed in native PHP.
Therefore, it is expected to take almost as much time as it would take to build a framework from scratch. The design structure should be kept as simple as possible, aiming for high-speed processing using JIT, and an all-in-one package that does not require many modules.
It should be an all-in-one package that does not require many modules. This will reduce the cost of installation, ease of installation and development, and allow web applications to be built up with simple GUI operations and a small amount of PHP+JavaScript proficiency or even zero.
The initial production will use Postgresql as the RDBMS, but eventually Oracle, MySQL, and SQL Server (covering all major RDBMS that can handle JSON and use SQL) will be supported.
Table define and relation
