Your keys
You hold them. People, software assistants, and the person who approves a change each have their own. Changing a key does not erase the old history.
Charleston, SC · Lowcountry, Myrtle Beach to Amelia Island
The SI is on a faster clock than your infrastructure.
I design and run the network, the computers, and the storage for one client at a time. I also build the workspace where your people and your software assistants do the job together, and leave a history you can check. When a job should have no screen of its own, I build a headless service the assistant can call, facing the company, the client, or both. One client. Built for that client. A handoff you can prove.
- checked · waiting for the picture
Live picture · company, client, no screen
01 · why now
A yearly plan for the equipment is already behind the work.
Switches, computers, and disks still get replaced on a calendar. The work moving across them does not. Companies now need many computers combined into one interface, a private network they can reach from anywhere, and software assistants that do real jobs. If the last plan was a server room and a firewall, it is behind. The moving lines below are that gap. They are not a score.
The line is a typical yearly refresh. Everything moving past it is already happening. The computers have to keep up with the network, or the new work has nowhere to run.
02 · the specialty
Share one workspace. Keep a history that cannot be quietly changed.
- what
- switch to the new system
- who
- software assistant
- check
- a person has to sign
- fingerprint
- 7f3a9c1eb2
This record checks out.
This is not a chat log a vendor can edit, export, or lose. A person or a software assistant writes what they did and signs it. A carrier delivers the note. Old notes are not edited.
You keep the keys. I cannot lock you out and call that your account. Change one character in an old note and the signature no longer matches, so the history cannot be quietly rewritten. Try it on the sample.
People and software assistants use the same workspace. The assistant has its own key, the same as a person. If the change matters, a person has to sign before it counts. That covers a switch to a new system, a password change, or an undo.
The carrier is only the delivery. Run it on your network. Replace it later. The history does not have to move with it.
You should be able to check the history without taking my word for it, or the carrier's, or the assistant's.
03 · built for you
Built for you. Not a seat in someone else's product.
A shop floor and a field crew do not keep records the same way. They should not be forced into the same software. I set up four things, then I stop adding features.
The carrier
It runs on your network, or only your network can reach it. You can swap it later. The history is not stuck inside the box that delivered the notes.
The allowed notes
The kinds of notes the history is allowed to contain. A go-live, a stop, a password change, a field note. If it is not on that list, it does not get to look official.
The approval
Which actions need a second signature before they count. That rule is yours. It is not a checkbox buried in someone else's admin screen.
04 · what I actually run
The shared workspace only works if the equipment under it is real.
A place for people and software assistants does no good if you cannot reach the network, the computers cannot take a graphics card, or a bad change cannot be undone. This is the equipment work, from systems I run myself.
The computers
I combine many computers into a single interface. They do not have to be the same kind. A graphics card can be given to one of them when the work needs it. I tested this on mixed hardware on purpose. Client hardware is mixed too.
The disks
The disks are planned with the computers, not added the week the first one fills up. The computers reach those disks over the network.
A ready box
A locked-down starting image that boots into the full setup, on separate networks so one service cannot wander into another. A first-run checklist. A health check that says whether the box is actually well. Each release is published with a fingerprint, so you can prove you got the file I said you got.
fingerprint 7f3a9c1e4b20d8aa
Getting in
A private network you can reach from anywhere, without opening the office to the internet. The connection is encrypted. Logins use a key, not a shared password. Admin rights are limited to the job. A remote desktop sits on a separate network when someone needs a browser on the box without opening the machine itself.
Data and passwords
A database, a fast scratch pad, and file storage. A separate password for each service. Passwords live in a vault, not in a file someone saved at 1 a.m.
How a change goes live
Changes are reviewed before they go live, the way a document is reviewed before it is sent. The switch happens without taking the system down. The previous version is kept, so we can go back. I try the change on a copy that only writes to a log before it touches the live system. The system I run has more than 300 automated checks.
Software assistants
Each software assistant gets its own key. They do real work on the systems. A person still has to approve the changes that matter.
Headless services
A service with no screen of its own, built for one job a software assistant does. I can face it toward the company, toward the client, or both. The company uses it inside the business. The client uses it without seeing your internal tools. Every call still leaves a note you can check.
05 · who
Independent since 2021. I run what I describe, so the claims can be checked.
I design and install the hardware and the software that runs on it. I am based in Charleston. I serve the Lowcountry, from Myrtle Beach to Amelia Island. You will talk to me, not to a bench of unnamed seniors. The computer groups, the fingerprinted releases, the health checks, the trial runs, and the approval step are things I run.
Before the contractor years I installed and commissioned home solar systems, including the inverters and the monitoring, and later led a 22-person regional sales team. I can talk to the person on the roof and the person who signs. This work often dies when it is handed from the person who sold it to the person who has to install it.
06 · the offer
A free look at your setup.
I will read your network, your computers, and your storage against how fast this work is actually moving. You get notes on what is fine, what is behind, and whether a shared workspace for people and software assistants belongs in the picture. If it does, the history has to be something you can check. Most hosted chat products cannot give you that.
You do not hire me to hear this. One working session. You leave with notes, not a slide deck.
Charleston, SC
Lowcountry, Myrtle Beach to Amelia Island