Architecture
This is a plain-language description of how Bloggity works, written for customers. It describes behaviour and guarantees, not implementation.
What Bloggity is
Section titled “What Bloggity is”A managed service. You point it at a product and it generates and hosts a blog for that product. You never run or maintain a site.
The pipeline
Section titled “The pipeline”- Onboarding — Bloggity reads your landing page and derives your Style System, Voice, and CTA, proposes Topics, and writes sample posts.
- Scheduling — Topics are placed on the calendar. Each day holds exactly one thing: a post or a research task.
- Generation — each post is written the day before it publishes, once any research scheduled ahead of it has finished.
- Publishing — posts go live at your publish hour.
Serving
Section titled “Serving”Your blog is served from a global network with per-post caching, so readers get it quickly wherever they are. Publishing a post invalidates that post’s cached copy, so your change goes live immediately rather than after a delay.
Custom domains connect with a CNAME record. Until you connect one, your blog is served at its preview address.
Your data
Section titled “Your data”- Content lives in Bloggity’s managed data store.
- Assets such as your logo and favicon are held in managed object storage.
- Domain routing is a lookup: nothing about your readers is stored to decide which blog to serve.
You can delete your account. A downloadable export of your content is not available yet. See T13 Export or delete your data.
Scheduling and background work
Section titled “Scheduling and background work”Background runs write the posts that are due every hour and publish due posts at your publish hour. The TODO queue only surfaces the work needed to keep your forecast window covered.
Research, at a high level
Section titled “Research, at a high level”Research gathers sourced evidence for your product and connects it to the articles it supports. When a research day is scheduled, it occupies a day slot instead of a post and costs the same as one credit.
Reliability and failure
Section titled “Reliability and failure”| Situation | What happens |
|---|---|
| Generation fails | The day slot stays open and the work is retried; nothing is published half-written. |
| Credits run out | Automatic generation pauses, manual actions are refused with a clear message, and your live blog keeps serving. |
| Payment fails | The blog stays online. New credit grants stop until the payment succeeds. See H3. |
| A domain is not available | Verification fails and the blog stays at its preview address. See H2. |
Security and privacy
Section titled “Security and privacy”- Post content is rendered through a sanitising pipeline, so generated markup cannot inject scripts into your blog.
- URLs fetched during setup are validated before they are used.
- Blog analytics are cookieless and contain no personal data.
A security and trust centre covering data handling, our data processing agreement, and service levels is planned.