Skip to content

the editor, live on this page

Build the tools and websites your business runs on.

Partials is a visual builder for internal tools, customer portals, landing pages, and full websites. Your own team builds it, engineers approve it, and it ships in days, not quarters.

Book a demoSee what teams built
components
150+
output
real tsx
runs
your cloud
POrder operations / Overview
Save
Order operations
Live view across web, mobile, marketplace and wholesale
Revenue today
$6,131
+8.4% vs yesterday
Open orders
5
-3 since 08:00
Refund rate
1.7%
+0.4 pts vs last week
OrdersSearch…
OrderCustomerStatus
ORD-31842
Nadia Haddad
Processing
ORD-31841
Omar El Khoury
Pending
ORD-31840
Lina Karam
Shipped
ORD-31839
Karim Nassar
Refunded
Revenue · last 14 days
Aug 27Aug 29Aug 31Sep 2Sep 4Sep 6Sep 8Sep 9
src/pages/overview/screen.tsxwritten by Partials
<Stat  label="Revenue today"  value="{{ '$' + orders.value    .filter(o => o.status !== 'Refunded')    .reduce((s, o) => s + o.total, 0)    .toLocaleString() }}"  change="+8.4% vs yesterday"  width={4} row={4} rowSpan={12}  canvasName="revenueToday"/>

What teams build with Partials

  • Internal tools
  • Customer portals
  • Landing pages
  • Company websites
  • Dashboards
  • Approval flows

shipped, not mocked

Real apps and real sites. No engineering backlog.

Every screen below is running in Partials right now, captured straight from the product.

  • A public marketing website for a coffee roaster built in Partials: navigation bar, a dark hero with headline and buttons, and a featured roast card.
    Marketing website
  • The published order operations app: four stats, a 14-day revenue line chart, orders by channel, and a table of orders with status tags next to a selected order panel.
    Order operations dashboard
  • A support inbox app with open, pending, and resolved tabs, a list of tickets with priority tags, and the selected ticket’s details and conversation.
    Support inbox
  • The pricing page of the same coffee website, with three subscription plans and their features.
    Pricing page
  • An inventory app with units on hand by warehouse, units by category, a fulfillment pipeline with five steps, and lowest stock levels as progress bars.
    Inventory and fulfillment
  • The team page of the support inbox app showing agents, their queues, and workload.
    Support team
  • The purchase orders page of the inventory app with inbound orders and their status.
    Purchase orders
  • The settings page of the order operations app with notification and threshold controls.
    Order settings

150+ building blocks, all live

Every block on this wall works. Go on, click one.

Tables, charts, forms, calendars, uploads, signatures. One consistent style, so nothing you drop on a page looks out of place.

  • switch01
  • rating02
  • segmentedControl03
  • ProcessingWebPriority
    tags04
  • progressBar05
    1. Picked
    2. Packed
    3. Shipped
    steps06
  • checkbox07
  • LiveDraftRefunded
    status08
  • switch01
  • rating02
  • segmentedControl03
  • ProcessingWebPriority
    tags04
  • progressBar05
    1. Picked
    2. Packed
    3. Shipped
    steps06
  • checkbox07
  • LiveDraftRefunded
    status08
  • Open orders
    5
    -3 since 08:00
    stat09
  • button10
  • NHOELKKN
    avatarGroup11
  • slider12
  • Customer
    NameNadia Haddad
    PlanWholesale
    SinceMar 2024
    keyValue13
  • input14
  • select15
  • dateInput16
  • Open orders
    5
    -3 since 08:00
    stat09
  • button10
  • NHOELKKN
    avatarGroup11
  • slider12
  • Customer
    NameNadia Haddad
    PlanWholesale
    SinceMar 2024
    keyValue13
  • input14
  • select15
  • dateInput16

how it works

Connect. Compose. Publish.

Three steps, whether it is a dashboard for your team or a website for your customers.

  1. 01step 1 of 3

    Connect your data

    Point Partials at the systems you already use. Orders, customers, files, whatever runs your business. Credentials stay safe on the server.

  2. 02step 2 of 3

    Compose the pages

    Drag headers, tables, charts, forms, and buttons onto a page. A dashboard or a landing page, same motion. Stuck on a piece? Describe it and the builder adds it.

  3. 03step 3 of 3

    Publish to the right people

    Your team, your customers, or the whole internet. Choose who can see, use, or edit. Nothing goes live by accident.

why teams switch

Why teams choose Partials.

One builder for what runs inside the company and what the world sees. Fast to build, safe to sign off, yours to keep.

  • Your team builds it. No ticket, no waiting.

    The people who know the work build the page. A refund desk for support, a landing page for a launch. Every piece is designed to fit together, so it looks right the first time.

  • Engineers sign off, gladly.

    Everything your team builds is real code your engineers can read and review. Nothing is locked inside a tool.

  • Nothing goes live until you say so.

    Work on a draft, see exactly what changed, publish when ready.

  • Safe with the data behind it.

    Who can see what is decided by you and enforced everywhere. Every change is logged with a name and a time.

  • Runs where you want.

    Keep it inside your own cloud, or let us host it. Same product either way.

  • Looks like your company, inside and out.

    Internal tools and public pages both feel like something your company made, because it did.

one workspace, four teams

Four teams. One builder.

Marketing, operations, support, and the warehouse each built what they needed, in the same place, from the same data.

The company website

Marketing publishes it on the company domain and changes the message the day the message changes.

A public marketing website for a coffee roaster built in Partials: navigation bar, a dark hero with headline and buttons, and a featured roast card.

trust

Built to be trusted with what matters.

Your tools and sites touch customers, money, and credentials. Partials treats that as the normal case, not an upgrade.

  • 01

    Your data stays yours

    Partials connects to your systems. It never copies your data somewhere else.

  • 02

    The right people, the right access

    Decide who can use, approve, or edit each app. It holds everywhere, not only on the screen.

  • 03

    A record of every change

    Who changed what, and when. Useful the day someone asks.

  • 04

    Credentials stay on the server

    API keys and connection secrets are encrypted at rest and never sent to a browser.

thirty minutes

See Partials on your own data.

We build a real page live from one of your systems and answer whatever you want to know.

Book a demoSee pricing