Is NocoDB ready for the Japanese market?
— a Tokyo native's gap map

GitHub issue #10394 (filed by KoutaHisano against v0.260.2) reports that pressing Enter to confirm a Japanese IME conversion is read as "create a new record." The issue is marked closed; the fix should be confirmed against the current release.

github.com/nocodb/nocodb/issues/10394

Japanese is typed through an IME where Enter confirms character conversion. If that same Enter fires "create a new row," every sentence risks junk records. A buyer who hits this in a trial concludes the product wasn't built for Japanese input and leaves — this is the most damaging single gap because it breaks the core action (data entry) for every Japanese user.

An isComposing check on the keydown handler so Enter is ignored while the IME is mid-composition. Verify the fix shipped and didn't regress across all input contexts in the current build.

nocodb.com and the pricing page render only in English. The community Japanese README is in the repo, not in the buying journey where it could help.

nocodb.com/pricing community jp README (repo only)

A Japanese team evaluating an Airtable alternative reads marketing in Japanese or moves on. When the funnel is English, the next team searching just finds Airtable's Japanese pages, or a local tool like microCMS, and goes with what they can read. The community README is invisible to them.

Japanese landing and pricing pages plus a language toggle, and pulling the community Japanese content into a place buyers actually pass through.

No 特商法に基づく表記 page found. The pricing page shows "100% secure payment" but doesn't name the payment processor.

nocodb.com/pricing

Japanese buyers look for the 特商法 disclosure before paying. It's the standard accountability check, and an unnamed payment processor adds to the hesitation. Without it, a careful buyer won't put a recurring charge on a company card.

A 特商法に基づく表記 page with required fields, and naming the payment processor on the pricing page. Both are small, known templates.

Plans are in USD: $0 free (up to 3 users), then $12, $24, and $45 per seat/month.

nocodb.com/pricing — USD confirmed

A USD recurring charge means exchange-rate uncertainty and a messier line on a Japanese invoice. For finance sign-off, a clean JPY figure is far easier to approve.

JPY display pricing, and a JPY invoice for the buyer's accounting where possible.

With no Japanese pages, there's nothing indexed against the terms a Japanese team searches. The community README is not accessible from the buying path.

A team wanting an open-source Airtable option searches 「airtable 代替」 or 「ノーコード データベース」. With no Japanese content, NocoDB doesn't surface, and they land on a local comparison article that may not even list it.

A few Japanese pages targeting those queries, including an 「airtable 代替」 comparison. The community README is a head start on raw material.

The Japanese README exists and reads reasonably, but there's no clear contributor or last-updated metadata, so there's no way to tell how current it is against the English version.

community jp README

A Japanese-language doc that's silently behind the English one can mislead more than help, and it reads as "they translated once and stopped." A careful buyer treats a stale-looking localization as a sign that Japan isn't actively supported.

Mark the translation's status and keep it in sync, or have a native speaker do a freshness pass so it reflects the current product.