Kanban
A drag is a real update
Moving a card writes the new status through the entity API, so permissions apply and any workflow watching for the change runs.
Switch any entity between a grid, a kanban board, a calendar, a map and charts in the Anythink dashboard, all on the same records your API serves.
Move order 1042 from packed to shipped.
The Anythink dashboard
Drag the card. The record updates.
The Anythink CLI
The same update, scriptable.
$ anythink data get orders 1042$ anythink data update orders 1042 \--data '{"status":"shipped"}'Claude, through MCP
Ask in plain text. The assistant runs the same commands.
you › “Mark order 1042 as shipped, then tell me which orders are still packed.”
Kanban
Moving a card writes the new status through the entity API, so permissions apply and any workflow watching for the change runs.
Map
The geo field that puts records on the map also powers radius search and nearest-first sorting in the search API.
Charts
Save a chart from an entity's Charts View and add it to a dashboard alongside materialised views and other widgets.
Import
Import a CSV from the grid with a saved column mapping, then switch views on the new records straight away.
Every view reads and writes the same entity through the same API and permissions, so nothing is copied and nothing drifts.
A spreadsheet-style grid with column filters, sorting and pagination. Turn on Instant Edit to change values in the cell, or import a CSV from the same screen.
Group records into columns by a select field, such as status. Drag a card to another column and Anythink updates that record through the API.
Lay records out on a calendar by a date or timestamp field to see bookings, deadlines and events at a glance.
Build column, bar, line, pie, funnel and cohort charts from an entity's fields, with counts or totals over time, then save them to use on dashboards.
Plot every record with a geo field as a pin and click through to the record. Field service, deliveries and listings read better on a map.
Views read and write through the entity API with the signed-in user's permissions, so changes made in a view trigger the same workflows as changes from your app.
How it works
A select field for a kanban board, a date or timestamp for the calendar, a geo field for the map.
Every entity opens in the grid. Switch with the view buttons above it: Grid, Kanban, Map, Calendar or Charts.
Edit cells in the grid, drag cards on the board, or click a pin or an event to open the record.
Build charts in Charts View, save them, and add them to a dashboard for the rest of the team.
See it switch
Open the same records as a grid, kanban board, map, calendar or chart.
Dashboards guide →Yes. Open any entity in the Anythink dashboard and switch to Kanban View. Choose a select field to group by, usually a status, then drag cards between columns to update each record.
Add a geo field and Map View plots each record that has a location. Calendar View uses a date or timestamp field, such as a booking date or a due date.
Each person's views are remembered in their browser: the view you pick for each entity, and the field a kanban board groups by, so teammates can each work their own way.
Charts you build in Charts View are saved in the project for everyone and can be added to dashboards.
No. Views are ways of looking at the same records. Switching views copies nothing, and edits made in any view go through the same API, permissions and workflows as your app.
Still have questions?
Get in TouchEvery feature reads from the same data model, so each one you add works with the rest.
The dashboard, the CLI, MCP and the SDK, plus guides for moving from other platforms.
How founders, agencies and enterprise teams use Anythink.
Guides and reference at docs.anythink.cloud.