Sometimes, markdown plus a database is enough.

Exotic CRUD server infrastructure for Datomic

Get Started →

Result: EDN?

Example registration form

email^†

name^†

age^†

birthdate^†

gender^†

Would you like a tee-shirt with that?

shirt-size^†

Change :gender to :female. ☝️

Shirt-size options

ident^†	gender^†	?e
	female
	female
	female

Pink solid borders indicate nested fiddles. middle-click a nested fiddle to drill down, or inspect it's source with alt-middle-click.

Interactive Hyperfiddle editor: EDN?

query^†

[:find  
 (pull ?e [:db/id :reg/email :reg/name :reg/age 
           :reg/birthdate :reg/gender :reg/shirt-size]) .
 :where 
 [?e :reg/email "dustin@example.com"]]

schema: $

See :fiddle/query examples and the Datomic query docs.

markdown^†

See :fiddle/markdown examples.

css^†

.-demo-hyper-control .alert { margin-top: 1em; margin-bottom: 1em; }

See :fiddle/css examples.

renderer^†

(let [{:keys [:hypercrud.browser/fiddle
              :hypercrud.browser/result]} ctx]
  [:div {:class class}
   [hyperfiddle.ui/markdown (:fiddle/markdown @fiddle) ctx]])

See :fiddle/renderer examples. ctx and class are in lexical scope. No (ns (:require ...)) yet so vars must be fully qualified.

links^†

rel^†	path^†	render-inline?^†	fiddle^†	formula^†
			edit	edit
			edit	edit (comp :reg/gender deref :hypercrud.browser/data :hypercrud.browser/parent)

See :fiddle/links examples.

Interactive, like Clojure

Model your schema and queries live, as fast as you can think. Experiment, stage, undo.

Data driven

Your application and its APIs are formally specified as data. Hyperfiddle uses your app specification to reify your APIs and basic UI scaffolding with core.match.

Invisible data sync

Hyperfiddle loads just the right data, automatically. Your app specification captures your API inter-dependencies as a graph, so data sync reduces to a graph partitioning problem. Hyperfiddle optimizes your service dynamically in ways hand-coded backends cannot.

Tool-assisted frontend dev

Both the Hyperfiddle and Datomic ontologies are semantic (like RDF), which means Hyperfiddle understands the structure of what you build. Concerns like routing, widget bindings, and CSS classes are automatic by default.

Cloud-native and immutable

Architected from the ground up for Datomic Cloud Ions. Each hyperfiddle is a static site, every API response served Cache-Control: Immutable, everything is proxied by CloudFront.

You do the work of four men in part-time. I have heard a lot of talk over my entire career in Silicon Valley but have never, ever seen anyone deliver like Hyperfiddle.
Ken, CEO

We had a go at making prototype on App Engine, Postgres database, HoneySQL, doing all these nested SQL queries. I haven’t spent a ton of time in SQL but I’m like, this is so stupid, why am I wasting time using anything but Datomic, and Hyperfiddle seems the natural way to build an app on top of Datomic. You’ve spent time figuring out how to glue the user interface to the data model, and all these things that a normal website needs, solved reasonably. This is something I wanna spend time understanding how to do.
Jeremy, founder

I want to use datomic for machine learning model management and I thought hyperfiddle may be a great way to build a UI that will visualize model metrics/performance. I use Datomic heavily day-to-day and am familiar with API design, but I'm not a web developer, which is a big sticking point for me.
Jerry, data scientist

I'm building a web/mobile app with a datomic-based backend, and we have a lot of server side data processing, ETL, need for manual data checking and admin and so on and it seems like rather than reinvent the wheel for all these "back of house" UIs it would be great to have something like Hyperfiddle solve that out of the box.
Dave, engineer