kintone review

Kintone is a hosted cloud workplace platform, not a library, CLI, or self-hosted server. It provides a visual environment for creating business apps, storing team records, and connecting discussions and workflows to that data. Teams can build apps with drag-and-drop tools, convert spreadsheets into collaborative databases, and configure approvals, reminders, task handoffs, and scheduled notifications.

In a typical stack, Kintone sits above a team’s data and process layer: staff use its interface to create and update records, while administrators define apps, permissions, and workflows. The platform also offers AI features for configuring apps, searching records, summarizing comment threads, and spotting trends. Kintone says proprietary and customer data are isolated and not used to train AI models. The homepage describes APIs, plugins, and third-party services as extension options, but does not establish Kintone as an API-first backend. Treat it as a hosted business application platform and validate integration and export requirements before using it as a system of record.

Kintone’s primary build surface is its drag-and-drop app and workflow interface. The product also lists APIs, plugins, and third-party services for extending apps and connecting systems. That gives developers potential integration paths, but the published product details here do not establish an API protocol, SDK, supported programming language, CLI, or webhook interface. Confirm those specifics in Kintone’s technical documentation before choosing an integration design.

The platform’s built-in features cover app forms, records, permissions, revision history, workflows, and conversations attached to data. That can reduce custom code for internal tools, but it does not answer how external services authenticate, handle errors, or stay within request limits. Ask Kintone for current API documentation, SDK support in your languages, rate limits, pagination and retry guidance, and plugin review requirements. Also check whether a required integration is available as a supported plugin or needs a custom connection. The available product description names APIs and plugins, but not protocol-level behavior.

Kintone has no free plan; the listed free trial is 30 days. The Professional plan is $16 per user per month and starts at five users. It includes basic features, 900 apps, 300 spaces, and 50,000 records per app. Custom is $20 per user per month, also starts at five users, and includes basic features, advanced customization options, 900 apps, and 300 spaces.

The pricing page says monthly or annual contracts are available but lists no separate annual rate. It also notes that sale pricing applies to first-time subscribers. Additional users are billed separately, but their price is not published. The pricing is seat-based; the listed materials do not give a request-based or compute-based charge. Optional extensions and Kintone Custom are listed as additional costs without prices, and automated batch processing requires an additional option whose price is also unpublished. Before budgeting for production, get a written quote for the expected seat count, extensions, and batch processing, and verify applicable record and API limits.

Kintone is presented as a cloud platform. The vendor's site lists no open-source license or self-hosted deployment option, so teams should plan around a hosted service unless Kintone confirms otherwise. That shifts infrastructure operation to the vendor but makes deployment and continued access dependent on the service.

The product description covers apps, records, files, permissions, and revision history, but does not describe a full data export format or migration process. Before storing operational or customer data in Kintone, ask which records, attachments, comments, permissions, and workflow configurations can be exported, in what formats, and whether export is available through the API. Migration difficulty will depend on those answers and on how much custom behavior relies on Kintone workflows, plugins, and app configuration. Keep an independent copy of critical data where your policies require it.

Kintone’s listed plan limits include 900 apps and 300 spaces on both Professional and Custom; Professional also lists 50,000 records per app. The Custom plan’s listed features do not state a per-app record limit. Confirm the applicable limits for your plan and ask about API request limits, throttling, and batch processing before integrating high-volume systems. Automated batch processing requires an additional option, with pricing not published.

The homepage describes granular permissions, revision history, and measures against vulnerabilities, unauthorized access, and login attempts. It also says proprietary and customer data are isolated and not used to train AI models. Those statements do not replace a review of contractual security, compliance, backup, recovery, and availability commitments. Ask for the relevant service documentation and escalation terms. For a production rollout, test your own workflows, access rules, export path, and failure handling, and establish what happens to integrations if a plugin or API call is unavailable.