Good questions.

liveblog.ai is a live blogging platform for newsrooms, publishers, and content teams. Prepare coverage, collaborate with your colleagues, publish updates as events unfold, and embed your liveblog on your own website so readers can follow the story.

You can cover any story that benefits from ongoing updates, including sports, news and politics, financial markets, weather alerts, product launches, and other live events. Prepare content in advance, publish throughout the event, and keep the coverage available for readers afterward.

liveblog.ai focuses on live coverage through text, images, and a continuously updated timeline. You can also embed videos and social posts within your updates. Use it for standalone live coverage or alongside a video stream to add key developments, background, and commentary.

Select “Get started” on our website or visit our contact page. Tell us about your coverage, team size, and website, and we’ll discuss a suitable plan and integration approach.

Existing team members can sign in to their workspace. If you’ve received a team invitation, follow the invitation process to join.

AI agent integrations are in development, and we’ll share more details later. We’ll provide MCP and Skills so you can work with liveblog.ai through your own AI agent. You choose your agent and decide which data it can access and which actions it can perform. Your data remains under your control.

The Early Partner Program invites teams with real coverage needs to help shape liveblog.ai. Partners use the product in their day-to-day work and share experiences, issues, and requests to help guide future improvements.

If you work in a newsroom, publishing organization, or content team and are happy to share feedback, contact us to express your interest.

We’d like you to use liveblog.ai in your actual workflow and share practical feedback: what works well, where you get stuck, what’s missing, and how those issues affect your coverage.

Feedback can come from a single task or an entire live event. We’ll agree on communication and participation arrangements with you before you join.

Early partners can speak directly with the product team and bring real-world needs into product discussions. Onboarding support, pricing, and usage arrangements will be agreed with each partner.

Yes. You can add live coverage to your existing website while keeping your site structure, branding, and reader experience.

We offer JavaScript and iframe embeds, as well as server-side rendering, a React SDK, and a Headless SDK for different integration needs.

If your website allows embed code, you can usually use JavaScript or an iframe for a basic integration. WordPress sites can use our plugin to add a liveblog through a block or short-code.

Server-side integration, custom reader interfaces, and more advanced website integrations generally require a developer.

Yes. Choose an official template and adjust the accent color, fonts, and light or dark appearance to fit your website.

If you need more extensive layout or component customization, contact us to discuss a suitable approach.

Readers don’t need a liveblog.ai account to view public liveblogs. They can read the coverage directly on the website where it is embedded.

If your website requires a login or subscription, access to the page remains subject to your website’s rules.

Yes. As long as your service remains active and the liveblog has not been archived, published coverage remains available for readers after the event ends.

Archiving removes the liveblog from public view while keeping it available to your team in read-only mode. You can unarchive it to restore public access.

Yes. Team members can work on the same liveblog, and members with editing permissions can collaborate on the same post in real time.

Assign roles based on each person’s responsibilities to control who can manage liveblogs, edit and publish content, contribute source material, or view the workspace.

Yes. Write posts ahead of time, set their scheduled publication times, and confirm them for publication. Editor, Board, and Calendar views help you manage content and schedules.

Scheduling a post does not automatically start a liveblog. An authorized team member must start the liveblog before its content becomes publicly visible.

Yes. Authorized team members can edit a published post and confirm an update. Changes being made in the editor do not immediately replace the version readers see; they become public once the update takes effect.

You can also correct published posts after the liveblog has ended.

We offer three monthly plans: Starter, Newsroom, and Publisher.

Choose a plan on our pricing page and contact us to discuss getting started. Pricing and included benefits are subject to the plan confirmed when your service is activated.

Concurrent liveblogs are the number of liveblogs your team can have open at the same time, including those being prepared and those currently live.

Page views count visits over a given period. Concurrent readers measure how many people are reading at the same time. Consider both your coverage schedule and expected audience when choosing a plan.

Each service uses its included allowance first. Usage within that allowance does not consume credits. Additional usage draws from your organization’s shared credit balance at the applicable rate.

Credits cover additional service usage; they do not increase member seats or concurrent liveblog capacity. Contact us if you need more credits or details about the applicable rates.

Contact us to discuss a larger plan or a custom arrangement. Share your team size, the number of liveblogs you expect to run at once, your estimated page views, and anticipated audience peaks.

You can also tell us about specific integration, branding, or support requirements.

Your team decides which content to publish, when to update it, and when to remove coverage from public view. Organization and team roles control access and actions within the workspace.

Drafts are not displayed as public coverage. Readers see content that has been published and is eligible for public access. Edits must be confirmed for publication before they appear publicly.

Use our contact page for product questions, feedback, or integration enquiries. Support included with each plan is:

• Starter: Email support.

• Newsroom: Slack support.

• Publisher: 24/7 Slack support.

When reporting an issue, include the relevant page, the time it occurred, steps to reproduce it, and screenshots where helpful. For early partnerships and product discussions, you can also contact our founder at jay@liveblog.ai.