Paddock

One widget library.
Endless products.

Here are three: Pulse, Feedback and SignWave, all built on Paddock, one library for widgets, dashboards and forms where the code you write runs in its own sandbox. Yours could be next.

Pulse's Company pulse wall: 2,078 orders today, €142k revenue today, 44 new sign-ups and 3,931 active now, revenue this year against last, and the quarter target, €1.39M booked of €2.00M.
Pulse
SignWave's Front desk at Hop House: a search for Isla Nash finds four waivers, three signed and valid, each with a Check in button, and one expired on 7 November, with Sign a new waiver; the day's nine check-ins are listed beside them.
SignWave

01 One library

Same editor.
Every product.

Pulse, Feedback and SignWave open the same widget editor and the same dashboard editor, from the same packages rather than copies. Improve the editor once, and every product built on Paddock has it.

The widget editor halfway through a wipe from Pulse to Feedback: on the left, Feedback's sidebar and its widget code; on the right, still Pulse's preview of CI & services, all operational. The layout, the Config and Code tabs and the preview are the same.

02 Widgets

Start from a block.
Make it yours in TSX.

Pick one of 220 ready-made blocks (KPI tiles, sparklines, gauges, charts), see it live with sample data, then change its code in the browser. The editor completes as you type and links to the libraries' own documentation. Click anything in the preview and it jumps to the line of code that draws it. The widget is code you own, not a settings screen.

The CI & services widget's code in Pulse's widget editor. Its first lines read: Started from the Pro block actions-cards: its tinted-icon cards as one row per service, under a headline for the worst state.
The editor's hover on a widget's icon prop: its type, the library's note on what it takes, and @see, a link to iconify.design's documentation for it.
Hovering a prop: the library's own note and link.
Inspect in Pulse's widget editor: the worker chip clicked in the preview, labelled widget.tsx:59:17, and the code beside it at line 59, the Chip that draws it.
Clicked in the preview: line 59 draws it.

03 Forms

Your own fields.
No account to answer.

A form field can be code you write: a 0 to 10 scale that colours each score, a tooth chart for a dentist, a car to mark scratches on for a hire firm. You write it in the same editor as a widget, with the same completions and documentation links. It is built and frozen with the version you publish, and customers answer through a link, with no account.

The 0 to 10 scale's own code in Feedback's field code editor: its TSX, with toneOf highlighted, the function that colours each score, 9 and 10 success, 7 and 8 warning, the rest danger.
SignWave's signing page for Larkfield Dental on a phone: a tooth chart, with teeth marked.
SignWave's signing page for Northway Car Hire on a phone: a car, with marks placed on its scratches.

04 AI

AI writes it.
You save it.

In Pulse, ask for a widget in plain words, or point at one and say what to change. Pulse's own AI and the Claude or ChatGPT you already use call the same widget tools. Every write is checked, then lands as a draft beside the tile. Nothing reaches a board until a person saves it. In our own designer, where new ideas are tried first, forms work the same way: click a field and say what to change.

Pulse's Add a widget panel over the Sales pipeline board: the request, a table of each sales rep with their deals closed this month, the value won against their quota and anyone below half of quota flagged, drawn with its sample data, and the reply.
The same panel after two changes: the money shown in euros, and, pointed at line 72, the Below half flags made solid red badges with a small warning icon. Undo and Try another way under the reply.
Changing the Pipeline by stage tile in words: the tile now, with a white €2.9M, beside the draft, with the figure green, and 1 change not saved beside the Save to board button.

Under the hood

Code that stays in its box.

Every widget and custom field runs in a sandboxed frame, with the library's own pinned versions of React and the charting libraries. Its code is compiled on the server, never in the browser. The frame's policy refuses requests to other websites, and a custom field can see only its own answer unless you allow it the whole form. We put it through a dedicated security pass, and we test it the hard way: a widget written to break out tries requests, sockets, beacons, images, navigation and WebRTC, and the outside server receives nothing.

The frame, from the library's source
<iframe sandbox="allow-scripts" …>

default-src 'none';
connect-src <runtime>/icons/;
form-action 'none'; frame-src 'none';
object-src 'none'; base-uri 'none'

widget-preview.tsx and build-srcdoc.ts; the script, style and image sources are left out.

Built on Paddock.

Pulse and Feedback started from the same starter app. SignWave started from Feedback.

Yours could be next.

Tell us what your business needs to show, collect or sign.