See what your developer shipped between calls
Three weeks. Another status call. You still do not know whether the money is working — only what you were told on the phone. You do not have to wait for the next call to know something happened. You open a link and it is there, with timestamps.
A public ship log
A read-only page that lists what was deployed and when. That is the whole page. No login for you, no board, no chat.
How it works
The developer connects the project. When something deploys, it lands on the log. You get a link. You open it in a browser — no account of your own, no software to install, nothing to chase.
What it does not do
It is a record of what shipped and when. It is not a progress bar against scope. It does not say whether the project is on schedule. A busy week is not automatically a good week. You draw the conclusions; the log does not draw them for you.
Who can find the page
The page is reachable by link. Search engines are not told about it unless the project owner turns that on.
This product’s own log
ErdiKnows runs the same public log for itself — not a mockup. erdiknows.com/p/ekfewmt9zr2ay
Who sets it up
Either the developer holds the account, or you hold it yourself and give the developer what they need to connect the project. When you hold it, the log stays with the project rather than with the person building it, and it outlasts a change of developer. Plans are on Pricing.
Ask for it
Paste this into a brief or a contract if you want the log on the project.
I'd like a public ship log for this project: a page that shows what was deployed and when. A link is enough for me — I don't need an account or anything installed. Beyond deploying as you already do, I don't expect a separate status report for this.
If you are the developer
The log shows event titles and dates — not diffs, not hours, not time tracking. It replaces the status email rather than adding to it. Erdi shows the markers and the window around a change. You decide what mattered.