Post Falls, ID · Software & automation tools · Remote (U.S.)

Software you can run—not slides about it.

Sweitzer Automations ships open-source tools: browser dashboards, a Chrome extension, Linux launchers, and workflow code you can inspect on GitHub. Based in Post Falls, Idaho; work is remote and available anywhere in the United States. There are no past client field jobs listed here—only what exists in the repos.

Start a conversation What we offer Software Downloads

About Sweitzer Automations

Sweitzer Automations is run by Timothy Sweitzer, based in Post Falls, Idaho (83854). Today the focus is software: tools published as open source, dashboards you can run locally or in the browser, and automation helpers built in public code—not a backlog of undisclosed field projects.

We do not advertise control panel fabrication, on-site system integration, or traditional on-site PLC/SCADA field services as completed work. If that changes in the future, this site will say so plainly. What you can verify today is in the GitHub repositories linked from this site.

Industrial automation is the domain we design tools for as we grow—not a claim that every industrial service on a generic brochure has been performed for a client.

  • Honest scope What’s shipped is what’s in the repo—no fake case studies.
  • Straight talk Remote-first, clear about what’s code vs. what would be a future engagement.
  • Build in the open Downloads, docs, and source links so you can evaluate before you reach out.

What we offer

Sweitzer Automations is a software-first practice today: tools you can clone, run, and extend—delivered remotely to clients and collaborators anywhere in the United States. This is not a catalog of completed field retrofits; it’s what we build and ship in the open.

  • Dashboards & analytics UIs

    Browser-based dashboards (Revenue Pulse, Flip tracker) and supporting Python tooling—local servers, Tk launchers on Linux, and static assets you can host yourself.

  • Browser tooling

    Chrome extension work (Manifest V3) to bundle documentation and plant-floor-friendly UIs in the browser—no proprietary runtime required.

  • Remote collaboration

    Scope, implementation, and delivery via email, video, and GitHub—Pacific Time based in Post Falls, scheduling aligned to your team wherever you are in the U.S.

Location & how we work

The business is based in Post Falls, Idaho (83854), but engagements are remote-first and available throughout the United States. There is no “150-mile radius” or implied on-site panel build—coordination is by email, video, shared repos, and shipped software.

  • Home base. Post Falls, Idaho · ZIP 83854 · PT (same as Los Angeles / Seattle).
  • United States (remote). Project work, support, and delivery are structured for distributed teams—timezone and availability are agreed per engagement.
  • What we don’t claim here. Control panel fabrication and on-site system integration are not listed as services we’ve performed for clients; the site stays aligned with what exists in public code today.

How we work

A software lifecycle: understand the problem, ship something inspectable, iterate with your team—without pretending we’ve already run your plant floor project.

  1. Discover Short call or written brief: goals, constraints, data sources, and how you’ll run the tool.
  2. Design & scope Wire the minimum useful UI or script, agree on repos, hosting, and acceptance checks.
  3. Build & document Implement in the open where possible; READMEs and downloads that match what’s on GitHub.
  4. Support & iterations Bug fixes and small enhancements as agreed; docs and source stay in the repo.

Skills & stack

What Timothy Sweitzer actually builds today—reflected in the Sweitzer Automations 3-22-26 repo and related open-source work. This is not a list of completed client field jobs; it’s the technical surface area for software engagements and tools.

  • Python. Analytics engines, CLI tooling, tests (pytest), and scripts to serve dashboards locally or on Linux.
  • Web front ends. HTML/CSS/JS dashboards, full-screen operator-style views, and static assets bundled for local or extension delivery.
  • Chrome extension (MV3). Unpacked extensions, bundled UIs, and in-browser workflows for technicians who live in the browser.
  • Linux & shell. Launchers, small HTTP servers, and “plant terminal” style workflows documented in-repo.
  • Automation & CI-minded workflows. Repo hygiene, reproducible setups, and clear docs so others can run what you ship—not black boxes.
  • Domain context. Interest in industrial and operational problems (metrics, flip tracking, revenue views)—without claiming delivered PLC/SCADA field programs or panel builds unless and until that’s true and stated explicitly here.

Project snapshot 3-22-26

This block tracks what the public website honestly reflects: software, open-source repos, and remote availability—not fictional case studies. Update it when you ship new tools or change positioning.

  • Brand & domain. sweitzerautomations.com, full SVG brand kit, favicon, and social preview image (Downloads → Brand).
  • Location & time. Post Falls, ID · ZIP 83854 · Kootenai County · Pacific Time — remote U.S. work (Location & how we work).
  • Services on the site. Dashboards & analytics UIs, browser tooling, remote collaboration (see What we offer)—aligned with GitHub, not with undisclosed field projects.
  • Contact. Inquiry form, email hello@sweitzerautomations.com, and phone (208) 295-8750 — hook the form to your host (e.g. Netlify) when you deploy.
  • Linux. Dashboard launcher scripts (linux/run_dashboards.sh, linux/serve_dashboards.sh) — see Downloads and LINUX.md on GitHub.
  • Chrome. Unpacked MV3 extension with bundled Revenue Pulse / Flip tracker UIs (chrome_extension/) — see Downloads and CHROME.md on GitHub.
  • Add next (when you have them). More product ZIPs/PDFs in public/downloads/ with matching rows in Downloads; certifications; industries served; client logos or real project write-ups—only when you can show them truthfully.

Software

This is the substance of what exists today: open-source tools from the Sweitzer Automations 3-22-26 project—sales and flip dashboards you can run on Linux, plus a Chrome extension that bundles the same UIs. Source and full instructions are on GitHub; printable assets and a short overview live under Downloads.

  • Linux

    Tk desktop launcher or a simple local HTTP server opens Revenue Pulse and Flip profit tracker in the browser—the same dashboards as on Windows and macOS.

    Setup guide Listing on this site

  • Chrome

    Manifest V3 extension: load unpacked from chrome_extension/ in the repo to open bundled dashboards from the toolbar.

    Setup guide Listing on this site

Downloads

Product packages, documentation, and brand assets. Official logos live in public/brand/; add product files under public/downloads/, link them here, then rebuild before you deploy. Linux and Chrome guides point to the open-source Sweitzer Automations 3-22-26 repository on GitHub.

Brand

  • Logo mark (icon)

    Symbol only—headers, favicons, app icons, and small placements.

    SVG Download

  • Logo lockup — dark background

    Full wordmark for the website, video lower-thirds, and dark UI.

    SVG Download

  • Logo lockup — light background

    Letterhead, proposals, invoices, and white slide decks.

    SVG Download

  • Social / link preview image

    Wide banner for Open Graph and social shares (same artwork the site uses for previews).

    SVG Download

Products & docs

  • Linux — Revenue Pulse & Flip dashboards

    From the project repo: Tk desktop launcher or a simple local HTTP server opens the same browser dashboards as Windows and macOS. Requires Python 3; Tk optional for the GUI launcher.

    Linux Setup guide

  • Chrome — extension (bundled dashboards)

    Load unpacked from chrome_extension/ in the repo: opens Revenue Pulse and Flip profit tracker in Chrome with no local server required.

    Chrome Setup guide

  • Linux & Chrome — quick overview (text)

    Short printable summary: repo link, one-line commands, and pointers to the full guides above.

    TXT Download

  • Getting started (example)

    A small text file so you can confirm downloads work. Replace with your real product files when you’re ready.

    TXT Download

Adding more files: copy the download-row block in index.html, change the title, description, and href to match each file in public/downloads/. Run npm run build and upload the dist folder (or let your host build from Git).

Let’s talk about your next project

Share what you’re trying to automate or visualize, your timeline, and your stack if you know. Engagements are remote and available throughout the U.S. Timothy Sweitzer responds personally—weekdays, Pacific Time, unless you’ve agreed otherwise.

Prefer email? Sweitzer Automations — hello@sweitzerautomations.com
Call or text: (208) 295-8750