Schema, from a sentence

Describe the app.
Get the architecture.

Archy turns one sentence into a live entity diagram — tables, types, keys and relationships — then generates the Prisma schema, TypeScript types and SQL.

Or start from

Working from

“a ride-sharing app with riders, drivers, rides, vehicles and real-time payments”

resolved

ride-sharing.archy

5tables5relations

users5

PKiduuid
emailstring
full_namestring
phonestring
created_atdatetime

drivers5

PKiduuid
FKuser_iduuid
license_nostring
ratingdecimal
is_onlineboolean

rides6

PKiduuid
FKrider_iduuid
FKdriver_id?uuid
statusenum
fare_centsint
requested_atdatetime

payments5

PKiduuid
FKride_iduuid
amount_centsint
providerstring
captured_at?datetime

vehicles4

PKiduuid
FKdriver_iduuid
platestring
modelstring

foreign key → references·drag a table·hover to isolate

Generated code

5 tables · 5 relations

schema.prisma77 lines

1// Generated by Archy — https://archy.dev
2// Source prompt: "a ride-sharing app with riders, drivers, rides, vehicles and real-time payments"
3
4generator client {
5  provider = "prisma-client-js"
6}
7
8datasource db {
9  provider = "postgresql"
10  url      = env("DATABASE_URL")
11}
12
13enum RideStatus {
14  requested
15  active
16  done
17}
18
19model User {
20  id         String    @id @default(uuid())
21  email      String    @unique
22  fullName   String    @map("full_name")
23  phone      String    @unique
24  createdAt  DateTime  @default(now()) @map("created_at")
25  driver     Driver?
26  rides      Ride[]
27
28  @@map("users")
29}
30
31model Driver {
32  id         String     @id @default(uuid())
33  userId     String     @unique @map("user_id")
34  licenseNo  String     @unique @map("license_no")
35  rating     Decimal
36  isOnline   Boolean    @map("is_online")
37  user       User       @relation(fields: [userId], references: [id])
38  rides      Ride[]
39  vehicles   Vehicle[]
40
41  @@map("drivers")
42}
43
44model Ride {
45  id           String      @id @default(uuid())
46  riderId      String      @map("rider_id")
47  driverId     String?     @map("driver_id")
48  status       RideStatus
49  fareCents    Int         @map("fare_cents")
50  requestedAt  DateTime    @map("requested_at")
51  rider        User        @relation(fields: [riderId], references: [id])
52  driver       Driver?     @relation(fields: [driverId], references: [id])
53  payment      Payment?
54
55  @@map("rides")
56}
57
58model Payment {
59  id           String     @id @default(uuid())
60  rideId       String     @unique @map("ride_id")
61  amountCents  Int        @map("amount_cents")
62  provider     String
63  capturedAt   DateTime?  @map("captured_at")
64  ride         Ride       @relation(fields: [rideId], references: [id])
65
66  @@map("payments")
67}
68
69model Vehicle {
70  id        String  @id @default(uuid())
71  driverId  String  @map("driver_id")
72  plate     String  @unique
73  model     String
74  driver    Driver  @relation(fields: [driverId], references: [id])
75
76  @@map("vehicles")
77}

Why it reads better

A diagram you can argue with.

Most generators hand you a wall of SQL and wish you luck. Archy shows the shape first — so the mistakes are obvious before they reach a migration.

Relations

Keys point at keys, not at boxes

Every edge anchors on the actual foreign-key row and terminates on the primary key it references. Cardinality is labelled on hover, so 1:1 and 1:many never get quietly confused.

orders

id
customer_id
total

customers

id
email
name

1:n

Output

One diagram, three targets

Prisma schema, TypeScript interfaces and Postgres DDL — generated from the same graph, with indexes and join tables filled in.

schema.prisma

types.ts

migration.sql

Canvas

Drag to think

Pull tables apart to untangle a hairball. Hover one to dim everything it does not touch.

rides

Types

Enums survive the trip

A status column becomes a Prisma enum, a TypeScript union and a CHECK constraint — all three, all consistent.

status enum [requested, active, done]
        ↓
type RideStatus =
  | "requested"
  | "active"
  | "done";

Speed

Nothing to install

The canvas, the generators and the copy button all run in the page. Paste the output straight into your repo.

Archy

Stop drawing boxes in Figma.

Describe it once. Drag it into shape. Copy the schema and go build the part that actually matters.

Try the canvas See how it works