Visual Database Designer

Design your data, get the API

Model entities, fields and relationships in the Anythink dashboard, the CLI or with Claude, and each entity gets a REST API the moment you save it.

The same task, three ways

Every task works three ways, and all of them change the same project. Here's one: an orders entity with a total and a status.

The Anythink dashboard

Point and click. Good for seeing the shape of your data.

The Anythink CLI

Repeatable, so the same model can be rebuilt in another project.

$ anythink entities create orders$ anythink fields add orders total --type decimal --required$ anythink fields add orders status --type varchar \--display select --options pending,paid$ anythink data list orders
  • ✓Entity orders created
  • ✓Fields: total (decimal, required), status (select)
  • ✓data list returns an empty page, ready for records

Claude, through MCP

Describe the model. It runs the same commands and shows what changed.

you › “Create an orders entity with a required decimal total and a status select with the options pending and paid. Then show me the entity and its fields.”

  • ✓Entity orders created
  • ✓total: decimal, required
  • ✓status: select with pending and paid
  • ✓Showed the entity and its fields

More than a table editor

Instant API

Save the entity, call the endpoint

Every entity gets list, get, create, update and delete endpoints with filtering, sorting and pagination, described in your project's OpenAPI documentation.

Secrets

Encrypted fields on any entity

A secret field encrypts its value with AES-256-GCM before it's stored, so a customer's own API token can sit on their record without being readable in the database.

Location

Geo fields work in search and on a map

A geo field powers radius and bounding-box search, nearest-first sorting, and the map view in the dashboard, with nothing extra to configure.

Operations

Materialised views join what a single table can't

Pivot an entity against another entity or your payments data, with exists, count or value columns and a total row across the whole project.

Model it once, use it everywhere

Entities, 18 field types, relationships, CSV import and materialised views, editable in the dashboard, the CLI or through Claude.

18 field types

18 field types

Text, rich text, selects, numbers, checkboxes, dates and timestamps, plus geo points, files, users, JSON and dynamic references. Each field's display type can change without changing how it's stored, so a text value can be an input, a select or a radio group.

How it works

From an empty project to a working data model

01

Create an entity

Name it in the dashboard, with the CLI or by asking Claude. Turn on row-level security or public read access when you create it, or later.

02

Add fields

Pick a field type, then mark it required, unique, indexed or searchable, or give it a default value.

03

Link entities

Add relationship fields between entities and choose what happens to linked records when one is deleted.

04

Load your data

Import a CSV with a saved column mapping, or create records through the API.

05

Use it

Call the REST API from your app, search it, and work with it in the dashboard's grid, kanban, calendar and map views.

See it working

Build the model by chatting

Describe an entity to the dashboard's AI chat and watch it appear in your data model.

Read the data modelling guide →

Frequently Asked Questions

What field types does Anythink support?

There are 18 field types: input, textarea, rich text, select, radio, country select, checkbox, short date, long date, timestamp, JSON, geo, file, secret, relationship, entity select, user and dynamic reference.

Underneath, values are stored as varchar, integer, bigint or decimal (each with an array variant), text, boolean, date, timestamp, jsonb, geo, file, user or a relationship type. Changing a field's display type doesn't change how it's stored.

Can I create relationships between entities?

Yes. Add a relationship field and pick one-to-one, one-to-many, many-to-one or many-to-many, or a dynamic reference that can point to records in different entities. You choose the on-delete behaviour (cascade, set null, set default or restrict), and related records come back through the same entity API.

Do I need to write SQL or migrations?

No. Creating an entity or a field from the dashboard, the CLI or an AI assistant changes the schema for you, and the REST API reflects it straight away. Fields can be required, unique, indexed or searchable, and can have default values.

Can I import existing data from a CSV?

Yes. Open the entity, choose Import, upload a CSV and map each column to a field. Tick Save these mappings as a template and the next import with the same columns reuses it. Each import runs as a job whose status you can check in the import history.

Still have questions?

Get in Touch

More in the same project

Every feature reads from the same data model, so each one you add works with the rest.

Want to learn more?

Submit a request and talk to sales about getting you setup with your perfect account today