Recommended ways to use GROWI.cloud

〜Engineer Edition〜
engineer

We will explain the recommended usage of GROWI.cloud, an in-house wiki knowledge base management tool for system engineers and SEs.
It is also the preferred replacement and migration tool for Pukiwiki, Crowi, and MDwiki-DokuWiki.

Creating and sharing system design documents such as UML, table design diagrams, and specifications

document-explanation

Creating and sharing system design documents such as UML, table design diagrams, and specifications

GROWI.cloud is an internal wiki and knowledge base tool that allows you to embed spreadsheets and create diagrams (draw.io) all in one tool.

Therefore, system engineers and SEs can use just one GROWI.cloud tool to create and share UML, table design diagrams, specifications, and more, without having to use multiple tools.

All of this can be done with just one GROWI.cloud.

Furthermore, it allows for flexible customization, such as integration with self-made APIs and CSS customization.

Information sharing among multiple companies

information-sharing

Information sharing among multiple companies

GROWI.cloud, an in-house wiki and knowledge base tool, is a flat-rate service, so you don't have to worry about costs even if the number of engineers at partner companies increases or decreases.

Furthermore, real-time simultaneous editing of the created Wiki is possible, so information shared on GROWI.cloud can be discussed in real time, and it can be used to create and share minutes such as weekly and regular reports.

Additionally, by using LDAP authentication and IP address filtering (optional), it is possible to restrict use to specific environments of each company involved, thereby achieving a high level of security.

Used to share response information between engineers and support

information-sharing

Used to share response information between engineers and support

If you provide your own company's services or products and your support engineers and first line of contact are separate, your support engineers can use the in-house wiki/knowledge base tool GROWI.cloud to record and share the details of why they took a certain action and how they responded.

In addition, the real-time simultaneous editing function can be used to share discussions and thoughts among multiple people when a problem occurs, and to summarize how to respond.

Case study interview article for HIKKY Inc. (VR Corporation HIKKY),which introduced GROWI.cloud for user support,see also.

Can be used as an alternative or migration tool for Pukiwiki | Crowi | MDwiki | DokuWiki | Confluence

replacement tool

Can be used as an alternative or migration tool for Pukiwiki | Crowi | MDwiki | DokuWiki | Confluence

GROWI.cloud, an in-house wiki and knowledge base tool, is a paid version of GROWI, an OSS development wiki forked from Pukiwiki and Crowi.

As a result, the usability and design philosophy are similar to Crowi and Pukiwiki.

Also, OSS services do not offer support, and there are no set, regular feature implementations or bug fixes, so GROWI.cloud is recommended for those who are considering switching from Pukiwiki|Crowi|MDwiki|DokuWiki etc. to a paid version of the service.

which actually considered Confluence and adopted GROWI.cloudA case study interview article from Internet Multifeed Co., Ltd.Please also see

Preserving and sharing the historical background of systems and services

information-sharing

Preserving and sharing the historical background of systems and services

The code only describes the current specifications,
sothere is no history of why the current design and code writing method came about

Especially in agile development, requirements are determined, coding is done, and then modifications and revisions are made. It is not appropriate to record the history of the implemented code as a comment, and tools
such as Jira and RedMine are not suitable as tools for recording history or past information, as they only record current requirements.

Therefore, by using the in-house wiki/knowledge base tool GROWI.cloud to record the history of code implementation on an MVC or function basis, it becomes possible to record past history, allowing engineers to understand the background of the implementation and think deeply about the implementation schedule, implementation order, and implementation content.

In addition, the timeline display function clearly displays the content created and edited by each engineer in a list.

Examples of features popular with system engineers and SEs
It can be used for various purposes, such as sharing information both internally and externally.
Template function
When you create a new page, you can have the subordinate pages inherit the specified template.
Timeline display function
It is possible to display the new creation and editing history of a page.
Embedding spreadsheets and charts
You can embed charts and spreadsheets you have created into Wiki pages.
Markdown support
It supports Markdown and allows for graphical page notation.
Tag search/full text search
Full-text search is possible, including the title of the uploaded file.
Real-time simultaneous editing function
It allows multiple people to edit simultaneously in real time.
Wiki history preservation
Edit history is automatically saved and past history can be viewed.
LDAP authentication and IP address filtering
To further strengthen security, we offer optional IP address filtering and basic authentication.

Price and supported features

SMALL
monthly amount(Exclude Tax)

¥8,000

Max user

per app

30
Number of apps
2
MEDIUM
monthly amount(Exclude Tax)

¥20,000

Max user

per app

100
Number of apps
3
LARGE
monthly amount(Exclude Tax)

¥50,000

Max user

per app

300
Number of apps
4
GRAND
monthly amount(Exclude Tax)

¥100,000

Max user

per app

1000
Number of apps
5
UNLIMITED
monthly amount(Exclude Tax)

¥200,000

Max user

per app

Unlimited
Number of apps
6
On-premise version availablehere
Price points and app ideas

GROWI.cloud's medium plan has a limit on the number of users that can use one app.
For example, with the medium plan, 100 people can use one app, and up to 3 apps can be used as standard, sofor ¥20,000 per month, up to 300 peoplecan use it.

Example Medium Plan
Price Point PC
Price Point SP A
Price Point SP B
If you would like to use more than 75 people in one app, please consider a higher plan.