The web stack, the automations, and any private model endpoint, held under one owner.
Registrar, DNS, certificate, host, mail records, mail authentication, business profile, form endpoint, payment keys. One of them expires on a date. The rest fail for their own reasons, on nobody's calendar, and the failure is usually silent. Attacks get the attention. Lapses do the damage, and nobody writes about them because there is nothing to write.
Most owners can name the first two and go quiet. The other seven are usually held by somebody they no longer talk to.
| Account | What it controls | What happens when it stops | Who holds it today |
|---|---|---|---|
| Domain registrar | The name itself | The name returns to the market and anyone can buy it | |
| DNS zone | Which servers the name points at | The site and the mail both stop resolving | |
| TLS certificate | The padlock | Browsers put a full-page warning in front of your homepage | |
| Host and CDN | Where the files live and how fast they arrive | Pages stop loading, or load from a cache nobody can clear | |
| MX records | Where your mail is delivered | Mail bounces back to whoever wrote to you | |
| SPF, DKIM, DMARC | Whether your mail is believed | Your invoices land in spam and a customer tells you before you notice | |
| Google Business Profile | The pin, the hours, the phone | The listing drifts, or somebody else claims it | |
| Form endpoint | Where a submission actually goes | The form says thank you and nothing arrives | |
| Payment keys | Whether a card can be charged | Checkout fails on the last step, silently |
A calendar carrying all nine renewal dates, with the certificate flagged thirty days out. A test submission through the form and a test call to the payment webhook after any change that touches either.
Questions and alerts reach one person's phone, and the habit is to answer the same business day. There is no operations desk and no SLA — the terms say so plainly. If you need somebody awake at three in the morning, say so on the first call and we will tell you that this is not that shop.
| Date | What changed | Who asked | What it touched |
|---|---|---|---|
| JUL 14 | Summer hours updated on the site and the listing | Owner, by text | Site, business profile |
| JUL 18 | Certificate renewed at twenty-one days remaining | Renewal calendar | TLS certificate |
| JUL 22 | Test submission run after form endpoint change | Us | Form endpoint |
| JUL 29 | Menu page replaced the PDF | Owner, by text | Site |
| AUG 02 | DMARC moved from none to quarantine | Us | Mail authentication |
Your site lives in version control and in the host's deploy history, so a bad change rolls back to a known-good version. That is what backup means here. Offsite backup and a tested restore are a separate thing, scoped on purpose and priced when you want them.
You text the change. It is made against the live source, deployed, and you get back the URL and a line in the log.
An edit is prices, hours, photos, a page, a seasonal menu. A build is new logic, a new integration, or money moving in a new way. We say which one it is before we start, and the log records which it was.
We register accounts in your name and on your card wherever the vendor allows it, and we tell you the ones where that is not possible and why. Anything sitting in an account of ours transfers to you on request. Ask, and you get the ledger with the logins: the domain, the DNS zone, the site source, the profile and the payment keys.
We do not hold a business hostage through its registrar. That is how most small businesses get stuck, and we would rather be kept than be difficult to leave.
Where a client has them, Operations also covers the automations running in production, the scheduled document ingest, and a private model endpoint. These are not included by default. They are covered once they exist.
Hub City Web is Oscar Napoles, a solution architect. Engineering is contracted per project to an independent systems engineer for the private infrastructure work. You speak to Oscar; the number in the footer is his.
The stack is standard components: a registrar, a DNS provider, a static host, a git repository, and on the private side an open-source index and a model endpoint. There is no Hub City Web software in the middle of it. You hold the accounts, and the runbook and credentials sit in a document you have a copy of from the first month. Another competent engineer picks it up from that document. The engineer on the infrastructure side is a contractor rather than staff, and his availability is confirmed in writing before we put a date on anything.
Operations runs $100 to $300 a month, set by how many properties we hold and how far we hold them. The catalog states what each rung adds.
Fifteen minutes gets you the list of your nine, who holds each one today, and the rung it prices at.