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 account holds the account kind and status, the customer, the service address and account number, every tank with its size in gallons, fuel, owned or leased, automatic or will-call, the heating and summer intervals in days, the route and stop, where to find it and its set and inspection dates as recorded, every delivery with the gallons, price per gallon, ticket and driver as recorded, every will-call request with its requested, promised and scheduled dates, every service call with its kind, the customer's words and its dates, every budget plan and pre-buy contract for a heating year as recorded, and an editable checklist.

Lastfill records accounts, tanks, deliveries, will-call requests, service calls, budget plans, pre-buy contracts and inspection dates as your office typed them. Overdue means only that the days since the last recorded fill are more than the tank's recorded interval for the season, and in the heating season a tank with no fill recorded since the season opened counts from the open date, so opening day starts every tank on its interval instead of flooding the board; Lastfill never estimates a tank level, a fill percentage or a run-out date, reads no weather, degree days, tank monitor or meter, and never says a tank, a regulator, a line, an appliance or an installation is safe or meets any rule. It plans no routes, dispatches no trucks, bills, charges or collects nothing, runs no autopay and messages no one. Gate, garage, door, keypad and alarm codes, passes, portal and tank monitor logins and passwords, budget plan autopay bank details, card numbers and Social Security numbers are refused in recorded text and in the native form drafts, whose answers are capped so the whole answer is checked, while tank sizes, gallons, prices per gallon, routes, stops, county roads and account numbers under six digits are accepted.

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.