CraftQL

Build SuiteQL against ground-truth, role-verified schema.

SuiteQL you can actually trust

CraftQL builds every query against your account’s real schema: the tables, the custom fields, and the columns the role that will run it can actually read. Not the documented schema. Yours.

It reads the truth from your live NetSuite account, role by role, completes and checks your SQL as you write it, then turns the result into a report your team can run and a tile on the dashboard, with nobody having to trust a guess.

CraftQL is patent-pending technology developed by YTBE, Inc.

Blind test against a live account

Asked to write a query against a custom record with no schema supplied, a frontier AI model invented every single field name.

Zero of its eight guesses existed, so the query could not run at all. On a common standard table the same model got nine out of nine right. That gap between stock tables and your own customizations and roles is the whole case for verifying schema against the account the query will actually run in. We ran that test ourselves, on a real account, and checked every identifier the model used against the account’s verified field catalog.

Product demos

See it running

The real interface, end to end. Each demo plays when you scroll to it. Pause it, step through it a beat at a time, or open it fullscreen.


Every NetSuite table, and which ones your role can actually read

Search every table NetSuite documents, then check one against your own login to see what you can really read. Candidate is a documented possibility; only a live check for your role makes it verified.

An editor that already knows your account

Tables, fields and functions finish themselves as you type, limited to what you are allowed to read, and checked before you ever press Run.

Put a trend on every row

Pick a trend from the column settings and CraftQL writes the query behind it. Your own SQL stays exactly as you wrote it.

Lay the report out by clicking and dragging

Click a column to change how it looks. Drag one onto the page to chart it. Every number you end up with came from the one query you already trust.

Drill from the number to the lines

Open any row to see the detail behind it. The report stays where it is, and the row you came from comes with you.

Know who can run it before you share it

Check the report against every role in your account before you send it, and see who is blocked outright and who would quietly be missing a column.

Ship it as a report, or as a dashboard tile

The same query becomes a report your team can run with ordinary filters, and a tile on the NetSuite dashboard.

CraftQL questions

The things people ask before the first call.