PEX

Open a plant export on your machine.

PEX is a local workspace for a PropertySync plant export. Search documents, auto completes, and land validations. Fix records, or rename an addition across the file. Then write a batch of just the changes. The original dump stays on disk until you save.

Talk to us about PEX

pex serve · 127.0.0.1 · TT-Spokane.db

What it does

PEX is for people who already have a plant-export file: plant operators, keying partners, and title companies hosted on PropertySync. It is a workspace, not a new plant host.

Search the export

Filter by instrument, party, addition, or legal. Open a record, edit the sheet, and move on. Related instruments open in place. The list is the plant, not a sample.

Mass updates

Rename an addition, a party name, or an instrument type across documents, auto completes, and land validations. Preview the hit count, then apply. Revert one record, or discard the whole session.

A batch of what changed

Export writes a PropertySync-shaped folder of created and updated documents, plus vocab and land validations when those moved. Deleted ids are listed separately. Unchanged images stay out of the batch.

If you already use ChatGPT, Claude, or Grok with tools, PEX can talk to the same local file. The plant does not have to be uploaded anywhere for that to work.

PropertySync first

PEX is built around the PropertySync export. We are adding TitleSearch and other batch formats so the same workspace can sit in front of more than one plant system.

PropertySync plant exports

Available now

Native today. Open the SQLite dump, work it, write a change batch in the PropertySync document shape.

TitleSearch transmissions

Building

Futura-style Export.txt plus Images/. In progress, so a TitleSearch dump can be a first-class PEX file too.

Other plant and search systems

Building

Batch files and vendor exports as we meet them. If we can read the plant, it belongs in the workspace.

Direct PropertySync posting

Building

The batch is the import today. Posting that batch into a live PropertySync plant is on the same path as the rest of TitleTools delivery.

How it works

Open the export

Point PEX at a PropertySync plant-export file. It copies to a working file and leaves the original alone. It only listens on this machine.

Search and edit

Navigate the plant, fix records, run mass updates. Watch the change count against the dump you opened.

Write the batch

Export a change folder: the PropertySync batch of modified documents, plus vocab and deletions when they moved.

Questions

Who is PEX for?+

People who already have a plant-export file and need to work it: internal plant ops, keying companies and partners, and title companies hosted on PropertySync. It is a workspace, not a new plant host.

Does the plant leave this machine?+

The workspace binds to localhost and reads the file on disk. You export a change batch when you want an import. Nothing is posted to a live plant until you take that batch somewhere.

Is it only PropertySync?+

PropertySync exports are native today. TitleSearch transmissions and other plant and search batch formats are being added so the same workspace can sit in front of more systems.

Can it post straight into PropertySync?+

Today PEX writes the batch import. Direct posting into a live PropertySync plant is the same delivery path TitleTools already uses elsewhere, and it is on the PEX roadmap.

How do I get it?+

Tell us which plant you work. We will get you a build. This is not a public download yet.

Want PEX on a real dump?

Tell us which plant you work and we will get you into the workspace.