A clear path
to your workspace.

Review unused starter additions for removal in Starter setup before removing the frontend. Server checks preserve edited or published workflows and pipelines with jobs or references. The process targets recorded kit additions rather than sweeping account records.

Preserve your local configuration and source edits. Preview frontend removal with node setup.mjs remove "/path/to/seedly" --dry-run. The automatic uninstaller uses a private restoration receipt and refuses to overwrite later edits. Keep that receipt private and out of public hosting or source exports. Removing frontend files does not remove account data or undeploy backend functions.

For an update, follow the documented removal/install process and reapply your preserved changes. A manually merged installation needs its own private change ledger and reviewed source rollback.

One contact-linked order holds the customer, the address and town, the parcel number with its label, the style, the size in feet, the siding, roof and trim colors, the model, how it gets there, the quote and base price, the signed order and deposit, the permit and site prep as recorded, the crew, build date, build days and arrival time, the build, the final walkthrough and its result, the outcome, the payment type and financing status as recorded, option lines and an editable checklist. One lot unit holds its stock label, spot, serial, size, colors, tag price, hold, sale and delivery.

Truebay records what your office wrote down. It makes no engineering, wind-load, snow-load, foundation, code-compliance or permit-approval claim, never decides whether a permit is needed, never inspects or approves a pad or a site, and processes no payment or financing. It does not design or price buildings, order materials, route trucks, schedule crews automatically, send texts, mail or calls, or reserve lot units. Gate, door, garage and keypad codes, portal and financing logins, Social Security numbers, dates of birth and card, security code and bank numbers are refused in recorded text and in the native form drafts, while building and door sizes, pitch, gauge, colors, model and serial numbers, prices, permit, parcel, lot and unit numbers, dates and phone numbers are kept. The guard catches accidental entries; it is not a guarantee against every way of writing a code.

The kit’s original operational screens share the frame with full CRM modules from your own Seedly source. Existing account permissions, feature gates, and configured providers still determine access to those modules.