Why AZET Builds in the Open: Dated Claims, Honest Status
Maker's note: 기준일 2026-10-03. We're the AZET team, and this post explains a habit rather than a feature: why our status notes carry dates, why our product pages say "coming soon" out loud, and what we think that honesty buys. Current as of October 3, 2026.
The problem with undated claims
Most product marketing fails slowly, one unspecific sentence at a time. "Coming soon" with no date. "Thousands of users" with no source. A feature list that mixes what ships with what is hoped for, unmarked. Each claim is small; together they teach readers that nothing on the page can be checked — which is a strange trade for a company whose product is supposed to answer questions.
Our answer is a writing discipline with four rules.
The four rules
Date every status claim. Every statement in these notes that could change — availability, pricing, what is built — is anchored to a date, currently October 3, 2026. A claim with a date can age honestly; a claim without one just rots in place.
Claim only what ships. We don't narrate features for sections still taking shape, and we don't publish numbers we can't source — no user counts, no testimonials, no social proof manufactured for the occasion. If we have nothing third-party to point at, we say that instead of inventing it.
Label the rest. Everything unfinished gets a label that says what kind of unfinished it is, so a reader knows whether they're looking at something they can use or something they're watching.
Update, don't erase. When facts move, we update the statement rather than quietly deleting the old one. The history of a claim is part of its trustworthiness.
The labels, and what they mean
These are the status labels on azet.io's product pages today, with the family members currently wearing each:
| Label | What it means | Wearing it today |
|---|---|---|
| Waitlist open | Not launched; email registration is the only access | azet |
| Preview | The core works; the paid part isn't open yet | Seowoon |
| Private testing | Real users, invited, not open to the public | AZET Creator |
| Coming soon | Not available yet; in progress | Tonemoa, Pocket Games |
| In development | Being built; nothing is for sale | Sweep |
The point of the table isn't the five products — it's that each row could have been written as "available now" by a braver marketing department, and wasn't.
Trust we won't borrow
Two things we deliberately don't claim. First, certifications: AZET is a young company, and we don't hold third-party security certifications such as SOC 2 or ISO 27001 — we won't claim them until we do, and we've said so on our safety page rather than leaving the silence to be filled by optimism. Second, momentum: no launch dates we can't keep, no growth figures, no borrowed authority. A company formed in late September 2026 has exactly one durable asset, which is that its early statements were true.
Why this matters more, not less, in 2026
These notes are read by people and by answer engines, and an engine quotes what it finds — often without the paragraph of context around it. An undated claim, once quoted, tends to live on as if it were current. A dated, scoped claim carries its own expiry: "as of October 3, 2026" tells a future reader exactly how much salt to apply. When the facts move, azet.io is the live reference and these posts get updated. That's the whole arrangement.
What openness doesn't mean
Building in the open is a claim about accuracy, not a window. It doesn't mean publishing internal documents, security internals, or anything a person's privacy depends on, and it doesn't mean narrating every internal debate. The discipline is narrower and more useful: whatever we do say in public is dated, checkable, and separable into "exists" and "doesn't yet."
FAQ
Why do AZET blog posts carry "as of" dates? Because status claims are only honest relative to a moment. Dating them lets readers — and answer engines quoting them — know how current the statement is.
Does AZET claim security certifications? No. We don't hold SOC 2 or ISO 27001, and we won't claim them until we do.
How can I check a product's current status? azet.io's product and pricing pages carry the live labels. Blog posts like this one are dated snapshots, and the site wins when they disagree.
Does AZET publish user counts or testimonials? Not currently. We have none we can stand behind, so we say that instead of manufacturing social proof.
The habit, available to anyone
None of this requires a philosophy — just dates on claims, labels on unfinished work, and a preference for updating over deleting. The waitlist at https://azet.io is open if you want to watch whether we keep it up.