Changelog - Hiveku Builder

October 2026

Email: the content of a sent email is kept 30 days

As of 2026-10-23, Hiveku removes the content of a sent email 30 days after it is sent: the message itself (its text and HTML), for emails sent through the Email Service, email marketing, automations, webinars and the help desk’s automatic emails (acknowledgements, ticket updates, satisfaction surveys and chat follow-ups). Who it went to, the subject, the status, and the opens, clicks and bounces stay, and your templates, campaigns and sequences are not touched. Help desk conversations and emails sent from a connected Gmail or Outlook inbox are not affected. Opening an email in Settings > Email Service > Email Logs shows its content for those 30 days; after that it says the content was removed. See Data Retention

Publishing: a broken publish goes back to the version before it

A broken publish goes back to the version before it: when the new version crashes or gives server errors on Hiveku’s check, the publish fails and, on Production and Staging, your site goes back to the version visitors had right before, usually within 1 to 3 minutes. Your changes stay saved, and it only happens during your own publish. When Hiveku cannot go back, the publish says so instead of “successfully deployed”. See When a new version fails Hiveku’s check
No more Instant rollback: it only moved a “Live” label and never changed what visitors see. To go back to an earlier version, use Roll back and put it live on the Branches tab, which rebuilds your site in a few minutes. See If a deploy goes wrong

Editor: checks and a preview for open reviews, and type check, lint and tests before merging

As of 2026-10-20, checks before merging: with Build before merging on, Branch settings can also run the site’s type check, lint and tests in that build, each answering on its own. A check the site has not set up is a warning; a failed test run is tried once more. See Checks before merging
As of 2026-10-20, checks on open reviews: on a site with Build before merging on, an open review from a branch that is not a draft has its branch built and checked once it has been still for two minutes, and the review shows the answer. The person who sent it hears when the checks fail, and Check again runs them again. See Checks on the branch
As of 2026-10-20, a preview for each review: an open review from a branch that is not a draft gets a live preview of its branch, which goes once no open review of the branch is left. It is started only where the development settings hold no live data and no keys beyond the short list previews are given, and one of a site’s five previews always stays free for people. See A preview of each review
As of 2026-10-20, checks never get live data: a check runs with the development settings minus any database staging or production runs with and minus keys with full access to the site’s data, and its log names what it left out. See What checks and previews are given
As of 2026-10-20, for AI tools: project_vcs_pr_get answers checks and preview and project_vcs_pr_list answers checks, project_vcs_checks_rerun runs a review’s checks again, project_test_build takes checks, and verify_typecheck, verify_lint and verify_run_tests take branch. See Branches and AI tools

Dashboards: Workspaces you can customize, role pages and more ticket buttons

As of 2026-10-14, Workspaces dashboards can be customized: Customize opens the same editor an account’s dashboard has, with a library of what can be counted across accounts, and the dashboard list keeps your own Workspaces dashboards. See The Workspaces dashboard
Role pages: Company overview (for owners and admins) and Finance join the whole pages, and the page made for your role is listed first. As of 2026-10-15, Sales, Marketing, Customers, Operations, Team, Technology, AI team and Security join them. See Role pages
Ticket lists can carry Assign to, Set priority and Move to queue buttons, each doing exactly what the inbox does. See Buttons and forms
Numbers within a minute: opening a dashboard again within a minute can show the numbers it read then; Refresh reads them again
As of 2026-10-16, a page you can see nothing on has no tab for you, and Share widgets split the dates’ whole without an earlier period, saying so when there is nothing to split. See Pages
As of 2026-10-15, the Workspaces page shows your clients as chips, four headline numbers (Form leads, Collected, Ad spend, Overdue tasks) and Pipeline and Ad spend columns in the portfolio. Two templates now carry real numbers (Ad spend across clients, SEO health across clients), and Decisions waiting is new. See The Workspaces dashboard
As of 2026-10-16, the default home has charts under its numbers: Website visitors for an account with a website, and Lead sources for an account that takes form leads. See Your dashboard
As of 2026-10-16, More > Copy link copies a link that opens at the page, dates and control choices on your screen. See Share and Publish
As of 2026-10-16, the widget library’s search understands your words: income finds Collected and Revenue, PPC every ad widget, vacation Time off, and a widget named exactly what you type comes first. See Customize a dashboard
As of 2026-10-16, a widget’s settings have a Style tab: the card’s background, border, corners and space, where the title sits, a line under it, an icon and an accent bar, and how its numbers are written (short or in full, decimals, below zero in brackets or red). See Style
As of 2026-10-16, lines, bars, shares and funnels can be read as a table, from the table button in the chart’s header, as heatmaps and combo charts already could. See Widgets
As of 2026-10-16, a page your role or plan doesn’t include says why when it brings you back to the dashboard, and who can change it. See Permissions
As of 2026-10-16, Workspaces reads each number once for up to 50 clients: every number on the default page (leads, pipeline, money, phone calls, ad spend, tickets and overdue tasks) is read for all your clients at once, instead of once per client, and your access in each client is looked up in one go. Each client’s number is the same one its own dashboard shows. See The Workspaces dashboard
As of 2026-10-16, ready-made widgets for what you pay vendors: Top vendors, How vendors were paid (check, ACH, wire and the rest) and Vendor payments made, counted the way Profit & Loss counts them. See Customize a dashboard
As of 2026-10-16, ready-made widgets for your Google Business Profile: Calls from Google, Direction requests, Website clicks from Google, Business Profile views, Calls from Google by day and Google Business Profile at a glance, for the locations Marketing > Listings shows. Google counts each day a few days late, so the newest days stay blank until it has, and a change compares the same days. See Customize a dashboard
As of 2026-10-16, ready-made widgets for what waits behind a paused automation: Deliveries waiting for a replay, Events waiting for a resume, Paused and still triggered and What waits behind each pause. Events a paused workflow held run when it is resumed; deliveries it accepted wait until someone replays them. See Customize a dashboard
As of 2026-10-16, ready-made widgets for your voicemail: Unheard voicemails, Voicemails, Voicemail messages, Voicemails by day and Voicemails by number called, counted the way Communications > Voicemail counts them. A caller who reached voicemail and left no message has nothing to hear, so that call is never counted as unheard. See Customize a dashboard
As of 2026-10-16, a Marketing attribution page joins the whole pages: new CRM leads, the deals won and revenue credited to channels, each channel from lead to revenue with its cost and return, and the visits and conversions of each landing page. Each deal is shared between the channels its people came through, by your account’s credit rule, as Marketing > Reports shares it. See Customize a dashboard
As of 2026-10-16, number tiles can carry colour rules: in Style > Colour rules, a tile’s number turns a colour when it, or its change, is above or below an amount, its goal, or what it was, and a line under the number says why. See Style
As of 2026-10-17, number tiles have options of their own: in Style > Number tile, a size from S to XL (an L or XL number steps down to fit a narrow tile), the number at the left or centred, the change as an arrow, a badge, a sentence or not at all, and the number day by day under it as a line, an area or bars. See Style
As of 2026-10-17, tables can carry colour rules: in Style > Colour rules, colour a number by a threshold, draw bars in a column, shade it by a scale, put an arrow on each change, or flag the rows where a number is past an amount. See Style
As of 2026-10-17, charts have options of their own: in Style > Chart, their colours, the line’s shape, a legend, the value axis (from zero, fitted, or set by hand), numbers on the points, gridlines, lines across (a goal or the average) and marked dates. See Style
As of 2026-10-17, ready-made widgets for your CRM contacts: Contacts, New contacts, New contacts by day, New contacts by first lead source, Contacts by lifecycle stage, CRM leads by status and Contacts by owner, counted the way CRM > Contacts counts them. A website chat visitor becomes a contact once they give a name, an email or a phone, and is counted from then. See Customize a dashboard
As of 2026-10-17, ready-made widgets for timesheets: Timesheet hours, Timesheet hours by day, Timesheet hours by person, Timesheet hours by project and People with timesheet hours: the hours logged on Accounting > Time. A pay run also pays time logged on tasks and paid time off, so it can show more hours. See Customize a dashboard
As of 2026-10-17, budget pacing widgets: Ad spend against budget, Ad budgets by ad account and Ad spend this month set this month’s ad spend against your ad accounts’ monthly budgets, with where the spend should be by now. Search the library for pacing. See Goals
As of 2026-10-17, AI search visibility widgets: AI mention rate, Mentioned in AI answers, AI mention rate by engine, AI visibility by keyword and AI visibility at a glance: how often ChatGPT, Perplexity, Claude, Gemini and Google AI Overviews mention your sites in the answers you track, by engine, site or keyword, counted as the AI visibility card on Marketing > SEO counts them. With no AI engines tracked, the widget links to Rank Tracking to set them up. See Customize a dashboard
As of 2026-10-17, two more department pages: Website traffic (visitors, sessions, bounce rate and session length, then visits by day, device, channel, landing page, referring site and country) and Profit and loss (revenue, expenses, net profit and margin, then profit by month, where the money went, profit by day and spending by category). Add one from Whole pages in the library, or start a dashboard with it. See Customize a dashboard
As of 2026-10-17, ready-made widgets for estimates: Estimates sent, Estimate acceptance rate, Accepted estimate value, Open estimate value, Estimates by status and Estimates sent by day: the estimates that went to clients in the dates (sent, or shared with Copy link and opened) and what became of them, and those still open, counted as Commerce > Estimates lists them. See Customize a dashboard
As of 2026-10-17, ready-made widgets for your AI receptionist: AI receptionist at a glance, AI share of inbound calls, Calls with a message taken, Calls with an appointment booked, Calls with a ticket opened and Calls with a booking by day: the phone calls your AI receptionist answered, its share of your inbound calls, and the calls on which it took a message for your team, booked an appointment that is still on, or has a helpdesk ticket, each call counted once. A number grid now shows the numbers you may see and leaves out the rest, rather than none of them. See Customize a dashboard
As of 2026-10-17, ready-made widgets for your plan usage: Plan usage, Allowances used up, Allowances nearly used, Allowances past the plan, Share of each allowance used, Contacts used, Automation runs used, Marketing emails used and Media storage used: how much of each allowance your plan includes is used right now (websites, team members, contacts, automation runs, emails, phone numbers and minutes, tracked keywords, AI images, storage, bandwidth and the rest), counted the way each limit counts it. Every member of the account can add them. See Customize a dashboard
As of 2026-10-17, widget settings offer only numbers you can see: a number your role or plan doesn’t include is greyed out, with the reason, so a widget you build never shows “No access”. See Widget settings
As of 2026-10-17, ready-made widgets for vendors: Vendors, New vendors, Paid to 1099 vendors this year, Paid to each 1099 vendor this year and 1099 vendors missing details: the vendors on Accounting > Vendors, what was paid to the ones marked 1099 as the 1099 summary totals it (each currency on its own), and the 1099 vendors still missing a tax ID or a mailing address. See Customize a dashboard
As of 2026-10-17, ready-made widgets for your ad account connections: Ad accounts connected, Ad connections to fix, Ad accounts with out-of-date numbers, Ad connections by status and Ad connections to fix, by account, and a Needs attention list, Ad accounts that need you: the ad accounts connected to Hiveku as Marketing > Paid ads counts them, the ones whose sign-in needs reconnecting or whose setup was never finished (nothing syncs for them), and the ones with a running campaign but no daily numbers for three days. See Customize a dashboard
As of 2026-10-17, ready-made widgets for recurring bills: Recurring bills a month, Recurring bills due in the next 30 days, Recurring bills running, Recurring bills by vendor, Recurring bills by expense category and Each recurring bill a month: the recurring vendor bills on Accounting > Recurring, what they come to a month, and their bills due in the next 30 days, with tax and discounts as the daily run makes them, each currency on its own. A recurring bill that is paused or ended, whose vendor was archived, or that has no line to bill is left out of the money. See Customize a dashboard
As of 2026-10-19, the Automations page shows the whole picture: the Automations department page grows from 3 widgets to 13: enabled automations, failed runs, the success rate and open dead letters; runs by day against the period before; runs and dead letters by workflow; and what needs a look (paused automations, ones on a failing streak, ones that cannot run, deliveries waiting for a replay, and what waits behind each pause). Add it from Whole pages in the library, or start a dashboard with it. See Customize a dashboard
As of 2026-10-19, ready-made widgets for calls by marketing source: Call tracking at a glance, Calls by source and medium, Calls by source, Calls by campaign, Calls by keyword and Call connect rate: your inbound phone calls by where each caller came from (the visit’s source and medium, else the tag on the number called), with how many connected, counted the way Communications > Attribution counts them. See Customize a dashboard
As of 2026-10-19, ready-made widgets for time off balances: Time off left, Time off balances below zero and Time off left by person: this year’s time off as the Balances card on Accounting > Time off gives it. A policy with no limit counts in the time used, never in what is left. See Customize a dashboard
As of 2026-10-19, ready-made widgets for calls from ads: Calls from ads, Calls from ads answered, Calls from ads by day, Calls from ads by campaign and Calls from ads by keyword: the phone calls your ad campaigns brought in, counted the way Marketing > Paid ads counts each campaign’s calls. See Customize a dashboard
As of 2026-10-19, ready-made widgets for your Hiveku bill: Owed to Hiveku, Hiveku invoiced, What Hiveku charged for, Paid to Hiveku, AI credit top-ups and Failed Hiveku charges. Only owners and admins see them, as only they see Settings > Billing. See Customize a dashboard
As of 2026-10-19, ready-made widgets for social profiles and posts: Social profiles to reconnect, Social followers, Social followers by network, Social posts published, Social posts published by day, Social queue at a glance, Social posts waiting for approval and Social posts failed: your connected profiles and your posts, counted the way Marketing > Social counts them. A post counts on each network it went out on. See Customize a dashboard
As of 2026-10-19, ready-made widgets for call queues: Call queues at a glance, Queue abandon rate, Queued calls by day, Queued calls by queue and Queue calls answered by: the calls that went into your call queues, how many were answered, how many callers hung up while waiting, and how many timed out, counted the way Communications > Call queues counts them. See Customize a dashboard
As of 2026-10-19, ready-made widgets for tracking number pools: Pools out of numbers, Pool numbers in use and Pool numbers free: how full your call tracking pools that are on are right now. A pool out of numbers shows visitors your main number, so their calls cannot be traced to the visit. See Customize a dashboard
As of 2026-10-19, ready-made widgets for call conversions: Call conversions at a glance, Call conversions waiting, Call conversions sent by platform and Failed call conversions by error: the tracked calls sent back to Google Ads, Google Analytics, Microsoft Ads and Meta as conversions, and which were accepted, refused, not sent or still waiting. See Customize a dashboard
As of 2026-10-20, a widget can look ahead: Tasks due counts the open tasks coming due, and a widget’s own dates can be the Next 7 days, Next 30 days, Next 90 days, Rest of this month, Rest of this quarter or Next 12 months. A number about what is coming is never compared with an earlier period, whose tasks have had longer to close. A ready-made Tasks due in the next 7 days widget is in the library. See Widget settings
As of 2026-10-20, the Team page shows the time off each person has left: Time off left by person now sits across the bottom of the Team page, this year’s balances as Accounting > Time off gives them. See Role pages
As of 2026-10-20, click to filter the page: press a bar, a part of a share or a table’s row to filter the page’s other widgets to that group, with a chip under the toolbar to stop. Each widget says what the click did to it, and a number set against a goal for its whole keeps its whole number. See Widgets
As of 2026-10-20, Approve and Reject on what agents are waiting on: the ready-made Agent actions to approve widget lists the actions the Sales, Support and Production agents staged for you, with Approve (for changes that can be undone in the app) and Reject on each, as Workflows > Pending actions has them. See Buttons and forms
As of 2026-10-20, ready-made widgets for contracts: Contracts sent, Contracts signed, Contract signing rate, Contracts waiting for a signature and Contracts sent by status: the contracts and proposals sent for signature, of those sent in the dates the share signed since, and how long they took. See Customize a dashboard
As of 2026-10-20, ready-made widgets for billing schedules: Active billing schedules, Schedules making an invoice in the next 7 days and Billing schedules by kind, as Commerce > Schedules shows them: an invoice counts on the day it is made, its due date less the schedule’s send lead. See Customize a dashboard
As of 2026-10-20, ready-made widgets for your support inbox: Conversations waiting for you, Live chats now, Conversations assigned to me and Inbox at a glance, each the count of its tab in the inbox. Assigned to me shows each person their own. See Customize a dashboard
As of 2026-10-20, ready-made widgets for your help center: Live help articles, Help articles published, Helpful vote share, Help articles by visibility and Help article views by category. See Customize a dashboard
As of 2026-10-20, ready-made widgets for what the assistant could not answer: Questions the assistant still cannot answer, Times visitors asked what it could not answer and Unanswered questions by where last asked: the questions of the last 30 days on the AI agent page, counted, never quoted. See Customize a dashboard
As of 2026-10-20, ready-made widgets for task dependencies: Tasks blocked by another task, Tasks ready to start and Blocked tasks by project: tasks that wait on other tasks. Blocked by another task is not the same as a task someone marked Blocked. See Customize a dashboard
As of 2026-10-20, ready-made widgets for task comments: Task comments, Client feedback on tasks and Task comments by who wrote them: your team, clients through a review link (counted since 22 September 2026), AI agents and automations. See Customize a dashboard
As of 2026-10-20, ready-made widgets for hours not on Usage yet: Billable hours not on Usage yet and Hours not on Usage yet, by project: the hours logged on tasks that are not on Commerce > Usage yet (hours already on Usage wait on its Unbilled tab). See Customize a dashboard
As of 2026-10-20, the Phones and bookings page shows the whole picture: it grows from 5 widgets to 12: Calls, Missed calls, Calls the AI receptionist took and Unheard voicemails across the top; then Calls by day beside Calls by source, Call tracking at a glance beside AI receptionist at a glance, Meetings at a glance beside Meetings booked by day, and Meetings booked by type beside Meetings held by host, the last three new in the library too. Add it from Whole pages in the library, or start a dashboard with it. See Customize a dashboard
As of 2026-10-20, ready-made widgets for your phone numbers and 911: Active phone numbers, Numbers with no route set, Numbers still activating, Phone numbers by where they ring, Local numbers missing a 911 address and Unverified 911 addresses. See Customize a dashboard
As of 2026-10-20, ready-made widgets for text messages: Texts sent, Texts received, Text delivery rate, Texts not delivered, Texts sent by day, Text conversations waiting, Text conversations waiting by person and Unread texts. A text scheduled for later counts as sent once it goes. See Customize a dashboard
As of 2026-10-20, ready-made widgets for review requests: Review requests sent, Review request click rate, Review requests by channel and Review requests at a glance: the asks for a review sent by email or text, from the Requests tab, a workflow, the support desk or a review funnel, and how many were opened and became reviews. See Customize a dashboard
As of 2026-10-20, ready-made widgets for review funnels: Review funnel completion rate, Review funnel journey and Review funnels: how many people began each funnel, finished it, opened a review site and left a testimonial (opening a site needs no finish, so the journey is a list of numbers, not a funnel). See Customize a dashboard
As of 2026-10-20, ready-made widgets for testimonials and private feedback: Testimonials collected, Testimonials waiting for review, Testimonials by kind, Testimonials at a glance, Private feedback received, Unhappy private feedback and Private feedback by how happy, counted the way Reputation counts them. See Customize a dashboard
As of 2026-10-20, calculated numbers: a widget can count a number worked out of its data’s own numbers, such as cost per conversion or a win rate. In its settings, open What to count and choose New calculated number. See Widgets
As of 2026-10-20, ready-made widgets for your email by day: Emails sent by day, Email open rate, Hard bounce rate, Spam complaint rate and Email health at a glance: the counters Email > Deliverability keeps, added up, each day a day in UTC. A rate over a few days can pass 100% after a large send, since an open or a bounce counts on the day it is recorded. See Customize a dashboard
As of 2026-10-20, ready-made widgets for drip sequences: Sequence enrollments, Sequence completion rate, Active sequence enrollments and Enrollments by sequence, counted as Email > Sequences counts them: one enrollment per contact and sequence. The completion rate of recent dates can still rise. See Customize a dashboard
As of 2026-10-20, ready-made widgets for your deploys: Deploys, Failed deploys, Deploy success rate, Average deploy time, Deploys by day, Deploys by result, Failed deploys by site, Time since the last successful production deploy by site and Deploys at a glance: the deploys Site > Hosting’s Recent Deployments lists, each counted once, with test builds and attempts Hiveku resumed after an interruption left out. See Customize a dashboard
As of 2026-10-20, ready-made widgets for builds published and site traffic: Builds published (by day, tier and site), and Bandwidth, Requests, Production and staging bandwidth, Bandwidth by day, Requests by day, Bandwidth by site, Bandwidth by tier and Site traffic at a glance, from the nightly count of what your sites served. A day counts once that night’s count has run. See Customize a dashboard
As of 2026-10-20, ready-made widgets for framework security: Sites at framework risk, Security fixes not deployed, Sites with an unverified framework, Sites to fix before publishing, Sites clear of framework advisories, Sites at framework risk by fix, Sites at framework risk by tier and Framework risk at a glance, as the Websites cards judge each site. Each tier is judged by the build its build list marks Live, which is not always the build visitors get. See Customize a dashboard
As of 2026-10-20, ready-made widgets for your sites: All sites, Live sites, Live hosted sites, Sites never deployed, Sites taken offline, Sites created, Sites by kind, Sites by live state and Sites by platform. All sites and Live sites match the Websites and Live sites counts of your dashboard’s Site summary. A site’s platform is read again from its files each time its preview starts. See Customize a dashboard
As of 2026-10-20, ready-made widgets for your pages: Pages, Published pages, Money pages, Missing meta descriptions, Pages added, Pages by site, Pages by type and Missing meta descriptions by site. Pages matches the Pages count of your dashboard’s Site summary. See Customize a dashboard
As of 2026-10-20, ready-made widgets for client feedback: Open feedback, Feedback open over 7 days, High or urgent feedback, New feedback, Feedback resolved, Median time to resolve, New feedback by day, Open feedback by site and New feedback by type: the feedback clients leave on your sites’ Review pages. Deleting its task on the PM board deletes the feedback too. See Customize a dashboard
As of 2026-10-20, ready-made widgets for saved versions: Versions saved, Versions made by AI, Versions saved automatically, Rollbacks, Merges, Time since the last version, Versions saved by day, Versions saved by site, How versions were saved and Time since the last version by site, as each site’s version history keeps them. See Customize a dashboard
As of 2026-10-21, ready-made widgets for your content: Content items, Content awaiting approval, Stuck content items, Content with a failed publish, Content items by status, Content items created, Content first published, Content first published by day, Content first published by author, Days to first publish and Content grounding, counted as Marketing > Content counts your posts. An archived post is never counted as a failed publish. See Customize a dashboard
As of 2026-10-21, ready-made widgets for your content calendar: Scheduled publishes waiting, Failed publishes needing attention, Published in the last 30 days, Publishing cadence, Publishes scheduled in the next 30 days, Publish dates nothing will run, Content calendar by day, Content calendar by kind and Published on the calendar by day, as the content calendar shows them. Failed publishes are not compared with the period before, because a publish someone has since dealt with leaves the count. See Customize a dashboard
As of 2026-10-21, ready-made widgets for content performance: Content page views, Leads from content, Content lead rate, Content page views by day, Leads from content by day, Most viewed content, Content bringing the most leads, Content page views by type and Content performance, from the nightly numbers each post’s Performance panel shows. See Customize a dashboard
As of 2026-10-21, ready-made widgets for your brand guides: Active brand guides, Brand guide completeness, Account-wide brand guides, Uploaded fonts with a problem and Brand guide checks. Completeness counts your account-wide guides, not a site’s own copy. See Customize a dashboard
As of 2026-10-21, ready-made widgets for your AI team’s turns: AI agent turns, Failed AI agent turns, AI agent turn success rate, AI agent turns running now, AI agent turns by day, AI agent turns by agent, How each AI agent is doing, AI agent turns by who started them and AI agents at a glance: each answer your AI team gave, by agent. A turn someone stopped is counted apart, never as a failure. See Customize a dashboard
As of 2026-10-21, ready-made widgets for how reliably your AI team runs: AI agent runs, Failed AI agent runs, Stopped AI agent runs, Failed AI agent runs (share), Average AI agent run time, AI agent errors, AI agent errors not recovered from, Failed AI agent runs (share) by day, AI agent errors by kind, How each AI agent ran and AI agent runs at a glance. One message to the website builder can be two runs, a quick first try and the full answer. See Customize a dashboard
As of 2026-10-21, ready-made widgets for the Communications agent: Communications agent today, Communications agent daily allowance used, Communications agent use, Communications agent use by day, Communications agent turns, Tool rounds per Communications agent turn, Communications agent use by kind and Communications agent use by person, measured against its daily allowance. See Customize a dashboard
As of 2026-10-21, ready-made widgets for billing notifications: Billing notifications delivered in the last 7 days, Billing notifications failed in the last 7 days, Billing notification delivery rate in the last 7 days, Billing notifications failed each day, Billing notifications waiting, Notification destinations switched off after failures, Billing notifications failed by event in the last 7 days, How each notification destination is doing and Billing notifications at a glance: the Slack and webhook notifications set up under Commerce > Settings, on its Integrations tab. Notifications are kept for 30 days. See Customize a dashboard
As of 2026-10-21, ready-made widgets for your social followers: Social followers by day, Net follower change, Follower growth and Net follower change by network, counted as Marketing > Social > Analytics counts them: each profile at its latest count on each day. See Customize a dashboard
As of 2026-10-21, ready-made widgets for how your social posts perform: Top social posts, Post impressions, Post engagement rate, Engagement rate by content pillar and Engagement rate by hook tag, from the numbers each post’s networks report. See Customize a dashboard
As of 2026-10-21, ready-made widgets for your content pillars: Content pillar mix, Social posts by content pillar, Posts short of pillar targets, next 30 days and Social posts with no pillar, as the social calendar counts them against each pillar’s target. See Customize a dashboard
As of 2026-10-21, ready-made widgets for text opt-outs and sending reputation: Numbers that opted out of texts, Text opt-out rate, Text failure rate, Numbers on the do-not-text list, Text opt-outs by day and Text opt-outs by stop word, as Communications > SMS counts them. See Customize a dashboard
As of 2026-10-21, ready-made widgets for texting registration: Can send texts, What stops texts, Texting campaigns by status, Verified toll-free numbers, Toll-free numbers by verification and Texting brand score, the same verdict the SMS registration page gives. See Customize a dashboard
As of 2026-10-21, ready-made widgets for phone usage and cost: Phone charges this month, Phone charges by type, Call minutes used this month, Share of included minutes used, Phone usage this month, Billed call time by number and Billed call time: calls and Talk live, counted as your phone bill counts them. See Customize a dashboard
As of 2026-10-21, ready-made widgets for your meeting types: Live meeting types, Booked in the last 30 days, Upcoming bookings, Booked in the last 30 days by type, Meeting types by who gets booked and Meeting types by way to meet, as the Meeting types page counts them. See Customize a dashboard
As of 2026-10-21, ready-made widgets for unsubscribes and opt-ins: Unsubscribed contacts, Unsubscribes by day, Opt-ins recorded and How contacts unsubscribed. See Customize a dashboard
As of 2026-10-21, ready-made widgets for suppressed addresses: Suppressed addresses, Newly suppressed by day and Why addresses are suppressed, the same list your senders check before they send. See Customize a dashboard
As of 2026-10-21, ready-made widgets for Shopify revenue from email campaigns: Revenue from email campaigns, Campaign orders by day, Revenue by campaign and Orders credited to a campaign, credited to the last campaign a buyer clicked, each currency on its own. See Customize a dashboard
As of 2026-10-21, ready-made widgets for marketing email readiness: Ready to send marketing email, What stops marketing email and Email sending suspended, the same checks as the Getting started list. See Customize a dashboard
As of 2026-10-21, ready-made widgets for refunds, voids and payment corrections: Refunded, Refunded by day, Payments refunded, Where refunds were made, Charges voided, Refunds awaiting confirmation, Payments removed and Payment corrections, from the rows Commerce > Payments lists. Each refund falls on the day it was made. See Customize a dashboard
As of 2026-10-21, ready-made widgets for sales tax: Sales tax collected, Sales tax collected by day, by rate and by month, Taxable sales collected, Non-taxable sales collected, Sales tax billed, Sales tax billed by rate, Taxable sales billed and Non-taxable sales billed, as Commerce > Reports > Tax summary counts them on money received and on invoices issued. See Customize a dashboard
As of 2026-10-21, ready-made widgets for customer lifetime value: Lifetime collected, Lifetime invoiced, Paying clients, Average lifetime value, Clients who paid the most, New paying clients by month and Lifetime value by first payment month, as Revenue by client counts them, each currency on its own. See Customize a dashboard
As of 2026-10-21, ready-made widgets for payment pages: Payment page views, Payment page payments, Collected on payment pages, Payment page conversion, Conversion by payment page, Payment page money after refunds, Payment page money by day, Payment pages by money taken, Declined payment page attempts and Abandoned payment page attempts, as Commerce > Payment pages counts them. See Customize a dashboard
As of 2026-10-21, brand offers are shown only to people who can read Marketing content: the Branding page and the brand guides the editor loads no longer carry a guide’s offers; the Offers tab loads them for people allowed to see them. Opening the Branding page now needs permission to view Branding.
As of 2026-10-21, Workspaces > Sites says “Finished … with errors” for every failed AI turn, including one that timed out or was cut off by a restart. A turn someone stopped is not an error.
As of 2026-10-21, Do not contact keeps a texted STOP: marking a contact Do not contact in the CRM no longer changes the source and date of an opt-out the person texted themselves.
As of 2026-10-21, the SMS page tells a turned-down texting campaign apart from one in review: when the carriers turned down your campaign, or it expired or was suspended, the page says so and points you to an appeal or a new campaign, instead of saying it is still being approved.
As of 2026-10-21, a campaign’s Revenue attributed card shows each currency on its own: it counts Shopify orders as the Orders page does, leaving out cancelled and test orders, and never adds two currencies together.
As of 2026-10-21, marketing email counts as set up only once it is switched on: an account whose sending domain was added through the email API now sees the Activate step in Getting started, instead of a ready sign that sending would refuse.
As of 2026-10-21, the follower widgets read Followers gained and Followers lost, and post performance and social engagement widgets refresh when a customer avatar, a before and after grid or a post changes.
As of 2026-10-22, refunding part of a Stripe payment refunds just that part: Hiveku sends Stripe the amount you enter, and the Refund dialog shows exactly what Stripe will be sent.
As of 2026-10-22, a refund that waited for Authorize.Net is counted once: whether Authorize.Net’s notice arrives first or someone clears the hold first, the refund is recorded once, on its payment. When Hiveku cannot match a notice to a refund it sent, it still records the refund and an inbox item asks someone to check it.
As of 2026-10-22, a text scheduled for a later month is billed once, in the month it is sent: a scheduled text is no longer billed while it waits, and one cancelled before it goes out is never billed.
As of 2026-10-22, Stripe imports record amounts correctly in every currency: payments, refunds and subscription prices in currencies such as yen, won or dinars are no longer off by a factor of 10 or 100, imported subscriptions show their own currency and billing cycle, and a row that cannot be imported is listed instead of stopping the import.
As of 2026-10-22, contract and proposal payments through Stripe charge the right amount in every currency: a payment block in yen or another currency without cents is charged at its price.
As of 2026-10-22, a refund Authorize.Net voids before it settles no longer counts as given back: the payment, its invoice and its deal go back to what they were, once, whichever notice arrives first, and an urgent item in your Commerce inbox says the refund did not go through and what to do. A refund on hold that Authorize.Net voided clears its hold. See Refunds
As of 2026-10-22, a Stripe refund that fails or is canceled no longer counts as given back: when Stripe reports that a refund failed (a closed card account, for one) or was canceled, Hiveku takes it back off the payment, its invoice and its deal, once, and an urgent item in your Commerce inbox says why and what to do. See Refunds
As of 2026-10-22, Slack and webhook notifications say when a refund was reversed: every destination that gets Refund issued also gets Refund reversed, with the amount and the reason, when a refund later turns out not to have gone through.
As of 2026-10-22, a text that never reaches the carrier is free: a text Hiveku could not hand to the carrier (stopped by a sending limit or an opt-out, or a send that failed before the carrier took it) is no longer billed. Received texts stay free. The Billing page tile reads Texts billed.
As of 2026-10-22, the Billing overview shows MRR and ARR in one currency: with subscriptions in more than one currency, the cards show the currency with the most MRR and list the others under the cards, instead of adding them together. The Subscriptions page’s Monthly recurring keeps each currency apart too. See Monthly Recurring Revenue (MRR)
As of 2026-10-23, texts are billed per segment, as the composer counts them: a text of up to 160 characters is one segment, or up to 70 with an emoji or another special character, and a longer text is billed for each segment. A picture message is billed for the segments of its words, at least one. Texts you receive stay free. The Billing page tile reads Text segments billed and shows how many texts they came from, and the invoice line reads SMS Outbound: N segments (M texts). See What a text costs
As of 2026-10-23, the Billing overview never adds money across currencies: with invoices, bills or subscriptions in more than one currency, every figure on the overview (what clients owe you, what you owe, MRR, net profit and margin, and both aging bars) is shown in one currency, the one most of your invoices from the last 12 months are in, and the other currencies are listed under the cards. Net profit and margin are worked out in each currency on its own; nothing is converted. Commerce > Reports > Sales does the same. See Monthly Recurring Revenue (MRR)
As of 2026-10-23, Hiveku reads your Stripe refunds once a day: a refund made in your Stripe dashboard, or one that failed later, reaches Hiveku even when Stripe’s notice never arrived. See Refunds
As of 2026-10-23, Hiveku tells you when Authorize.Net is not sending its notices: Hiveku asks Authorize.Net again every day for a webhook it could not register, and when Authorize.Net refuses (usually because the account has no Signature Key yet), an urgent item in your Commerce inbox says so and what to do. See Connecting Authorize.Net
As of 2026-10-23, a refund from Hiveku that does not reach you no longer counts as refunded: Hiveku emails you and shows a notice in the app, and its billing team contacts you to send the money another way. See Refunds
As of 2026-10-24, Hiveku tells you when Authorize.Net’s notices fail your Signature Key: when a notice from your Authorize.Net webhook does not match the Signature Key saved in Hiveku, an urgent item in your Commerce inbox says so and what to do, and it closes on the first notice that passes. See Connecting Authorize.Net
As of 2026-10-24, a blank key field keeps your saved Authorize.Net key: when you save your Authorize.Net settings again, enter only the keys that changed. A new API Login ID needs its own Signature Key. See Connecting Authorize.Net
As of 2026-10-27, a refunded AI credit pack takes back the credits it added: when Hiveku refunds a credit pack (one you bought, or one auto-recharge bought), its credits come off your AI credit balance in proportion to the refund, the refund email says how much, and the invoice counts only the share you kept toward the month’s AI credits. If the refund does not reach you, the credits are put back. Credits Hiveku’s team adds to your account count in full. See Refunds
As of 2026-10-27, a refunded auto-recharge pack no longer counts toward your monthly auto-recharge limit: a partly refunded pack counts only the part you kept, so auto-recharge can buy again within your limit. See Plan and usage
As of 2026-10-27, Hiveku tells you once about a refund that did not reach you: a later notice about the same refund, or a cancellation Hiveku itself asked for, no longer sends another “did not reach you” email. See Refunds

Fixes: recurring bills, ad connections, call notes and the Monday paid ads email

As of 2026-10-19, Accounting > Recurring shows each bill as it will be made: in its own currency with tax and discounts in, how often in words, a warning when no line will be billed, and Ended once a recurring bill has made its last bill. A recurring bill never makes a bill dated after its end date, and one past its end date says so instead of offering to start it again
As of 2026-10-19, a revoked Amazon Ads or Vibe sign-in is caught: the connection is marked for a reconnect and the account’s owners and admins are told, as for Google, Meta and Microsoft. See Reconnecting
As of 2026-10-19, processing a call’s recording keeps the AI receptionist’s notes: who called, how the call was screened and which AI department answered stay on the call’s CRM record, beside a person’s wrap-up
As of 2026-10-19, the Monday paid ads email keeps warning: a connection that needs reconnecting, or whose numbers stopped, is named for up to eight weeks, even in a week with no spend to report. See Reconnecting
As of 2026-10-20, dashboards name someone who has left the account in words: tasks and tickets split by who they are assigned to, and the Assign to button’s list, say Someone not in this account instead of the start of an id.

Paid ads: working Amazon Ads and Vibe connections no longer say “Token expired”

As of 2026-10-17, Amazon Ads and Vibe connections that work are no longer marked “Token expired”: their sign-in renews itself whenever Hiveku uses it, so Marketing > Paid ads > Connections no longer badges a working one as expired or asks you to paste a new token. See Reconnecting

Branches and publishing: one approval rule for everyone, and plainer words

As of 2026-10-14, “Require an approval” covers people too: with it on, a branch goes into Your site only through a review someone else approves. Merging a branch straight into Your site is refused for people as it already was for AI tools; Hiveku AI still merges after you approve its card. See Require an approval
A scheduled publish that waits says so: when the environment it deploys to shows a branch, the entry’s schedule reads “Waiting to publish” and names what ends the wait (setting that environment back to Your site), instead of “Last attempt failed”. See Scheduled publishing
Instant rollback in plain words: builds are named by when they were deployed, the confirm says what visitors see, and a team’s Slack hears that the environment “is back on an earlier build”. See Deployments

Dashboards: your home is a dashboard you can arrange

As of 2026-10-13, every account’s home is a dashboard: the numbers your business runs on (website form leads, open pipeline, money collected and overdue receivables) sit beside the familiar home blocks, and over 200 more can be added. Until someone customizes it, the home is built from the parts of Hiveku the account uses, so it grows with the account. See Your dashboard
Customize: owners and admins arrange the account home, and anyone can make dashboards of their own. Drag and resize widgets, add up to 10 pages, add controls that change many widgets at once, arrange the phone layout, and get back any earlier layout from Versions. See Customize a dashboard
Over 200 ready-made widgets, grouped by the question they answer, with Department and Shows filters. Rest the pointer on a widget (or press Preview on a phone) to see it drawn with sample numbers before you add it. Whole department pages (Leads, Money, Projects, Support, Phones and bookings, Reviews, Social, Automations) add in one step
Build your own from any number Hiveku keeps, or describe the widget in words and let Hiveku fill in the settings for you to check. New widget types: heatmap, scorecard, needs attention, full funnel, number grid, combo chart, gauge, bullet chart, movers and paths. See Widget types
Honest numbers: every widget says when its numbers are from, what it counts, and why a number is missing (not connected, not on your plan, no access) instead of showing 0. Each widget’s menu opens the page its number comes from and downloads its numbers as CSV
Share and publish: share a dashboard with the account, pick teammates who may change it, copy it into another account you are in, set any dashboard as your own home, or publish it to the account home. See Share and publish

Dashboards: your own data, buttons and forms

As of 2026-10-13, Your data holds the account’s own tables (Settings > Your data): running logs, latest values and tallies, with typed columns, CSV import, paste from a spreadsheet, and 30 days to undo a deleted row or a column change. Widgets read them like any other data and update within seconds. See Your data
New workflow step, Send to Dashboard, saves rows into a table, with two templates under Dashboards: Webhook to Dashboard and Check an API on a Schedule
New workflow trigger, Dashboard Button: any workflow can become a button on a dashboard. Lists of leads, tickets, tasks and deals can carry buttons on each row (Mark done, Assign to me, Resolve, Move stage and more), each doing exactly what the department page does. See Buttons and forms

Team activity, with a weekly leaderboard

As of 2026-10-13, owners can switch on team activity (Settings > Team activity): points for what each person does in Hiveku, squares for each day, a leaderboard with trophies and badges, and an end-of-week email to owners and admins. Nothing is counted until an owner switches it on, the team is told first, and it keeps only the numbers, never what anyone wrote or said. See Team activity
Settings > Team Members shows the team’s activity above the list, and Activity Log describes dashboard and sharing changes in plain words

Workspaces and AI apps

As of 2026-10-13, Workspaces opens as a dashboard: a portfolio of every client’s numbers with a totals row, your pinned views and module tables, plus agency templates such as Agency morning and Client sites needing attention. See The Workspaces dashboard
AI apps on your Hiveku key (Hiveku for Claude Code, Codex and the VS Code extension) can build and change dashboards, pages, widgets and Your data tables for you, with your role and plan. Deleting, publishing and sharing a dashboard, restoring an earlier version, and deleting a table or changing its columns stay with you in the app for now. See Build dashboards with AI

Branches: reviews, comments, the merge line, and three rules for how changes reach Your site

As of 2026-10-08, reviews take comments and approvals: on a review, people comment on single lines, reply in threads, resolve conversations, and Approve, Ask for changes or Comment. Only a person approves, never an AI tool, and nobody approves a review they opened. An approval counts for the changes it saw: new changes need a new approval. See Reviews and merging
As of 2026-10-10, each review shows whether it merges cleanly and whether it would conflict with another open review
Conflicts are resolved in the review: Choose what to keep offers Keep this branch’s, Use Your site’s or Edit for each file, saved as one version of the branch, then Merge again
A merged branch is archived: it leaves the Branches list and can be restored from the merged review for 30 days. See After a merge
As of 2026-10-09, the merge line: add reviews to the merge line and they merge one at a time, in order, each after it is checked to merge cleanly and to add no secret keys to code. Joining the line is the approval to merge; nothing goes live until you publish. See The merge line
Three Branch settings an owner or admin can turn on: Require an approval (from 2026-10-08: changes go into Your site only after another person approves them), Require reviews for outside AI tools (from 2026-10-10: Claude, Codex, VS Code and other connected AI tools work through branches and reviews instead of changing Your site directly), and Build before merging (from 2026-10-11: the merge line builds each review with Your site before it merges). See Branch settings
As of 2026-10-12, an approval link for AI apps that don’t ask first: on a site that requires reviews for outside AI tools, an AI app that does not ask you before adding a review to the merge line gives you a one-time link to approve or decline. See The approval link
AI agents: the project_vcs_pr_*, project_vcs_queue*, project_vcs_conflicts, project_vcs_resolve and project_vcs_settings tools do all of the above, the Claude Code plugin adds /hiveku:review-pr, and Hiveku AI asks with a card before it merges or adds to the merge line. See Branches and AI tools

As of 2026-10-09, every payment page has a type: How people pay asks for Open amount (the payer types what they owe), Fixed price (you set the price, or up to 8 prices to choose from) or Subscription, in the editor and in the New payment page dialog, and only that type’s settings show. The payment pages list shows each page’s type under its name. A page can be switched on only when someone could pay it (a price on a fixed page, a plan on a subscription page), and changing the type of a live link warns you first. A fixed price page with one price shows a clean “Amount due” block instead of a single button. See Payment Pages
Subscription pages: a page can sell one of your subscription plans. The payer pays the first period on the page, their card is kept, and the subscription starts with renewals charged to that card, exactly as one you create by hand. The button says Subscribe; the sentence above it names your business, the amount and the schedule, and its cancel line follows your client portal setting. The payer gets the “You’re subscribed” email and a receipt, and an email that already has an active subscription to the plan is turned away before any charge. You can create or edit the plan without leaving the page. On Stripe, a card that needs 3-D Secure can’t complete a paid sign-up yet; the payer is asked to try another card and nothing is charged. See Subscription pages
Free trials and a choice of plans: a plan with a free trial starts the trial on the page with nothing charged today, and the first charge comes when the trial ends; a free trial is offered once per person per plan. Let visitors choose offers up to 4 plans on one page. See Free trials
As of 2026-10-12, payers can choose how many, or how much: under What a payer chooses, a subscription page can let the payer pick a quantity (seats, users or locations at the plan’s price each, up to 1,000) or their own amount each period (like a monthly donation, with up to 6 suggested amounts). Every renewal charges what they chose. See What a payer chooses
Your own welcome email wording: a subscription page’s After payment section words the “You’re subscribed” email with a subject, a message that replaces the greeting, and tags such as {{payer_first_name}} and {{plan_name}}, with Send a test to me. The plan, its price and the first charge always follow your message. See Welcome email
Archiving a plan that pages sell: Subscriptions > Plans says which payment pages sell each plan, and the archive dialog names each page and what archiving does to it before you confirm. The page editor and the list say “plan archived” afterwards
AI agents: accounting_payment_page_get and accounting_payment_page_update read and change all of the above, including config.pricing.quantity, config.pricing.payer_amount and config.welcome_email
As of 2026-10-14, AI agents can create subscription plans: accounting_subscription_plan_create makes the plan a subscription or a subscription payment page needs, as New plan does. A plan with the same name is never made twice: the agent gets the plan that is there, with whether it bills what was asked, and asks you when it doesn’t. It works with a person’s own connected key (the VS Code extension, the Claude Code plugin from 0.27.46, Codex), when that person may create subscriptions. See AI agents and the API

Subscriptions and invoice payments: restarting Unpaid, and 3-D Secure on invoices

As of 2026-10-14, an Unpaid subscription can be restarted: attach a new card, set the Next billing date, then turn on Bill automatically under Edit. It is Active again, its declined periods count from zero, and it bills on that date. The date must be on or after the end of the last period already invoiced, so no days are billed twice; an earlier date is refused with the invoice and the earliest date named. Its history reads Billing restarted. See Failed payments
As of 2026-10-14, invoice payments on Stripe handle 3-D Secure: when a client’s bank asks for its own check while they pay an invoice from the payment link or the client portal, the bank’s step opens on the page and the same payment completes once it’s passed. Before, the client saw an error. If their connection drops right after the check, the next payment attempt or the automatic charge on the due date records that payment instead of charging the card again (or, when a payment was recorded on the invoice in the meantime, stops that charge once and asks you to check in your Commerce inbox). See Paying an invoice

Subscriptions: a staff free trial renews on the day it ends

As of 2026-10-09, a subscription created with Free trial first renews on the day its trial ends, the same way a payment page trial does, unless a renewal day was set through the API or an AI agent. See Subscriptions

Saved cards: the cardholder’s name goes with every card on Authorize.Net

As of 2026-10-09, cards saved on Authorize.Net carry the cardholder’s name, from the card form, the payer or the client, wherever a card is saved: payment pages, invoice payments, the client portal, the card-update link and cards your team adds
As of 2026-10-12, the name is one Authorize.Net can store: Authorize.Net keeps only Western European letters and turns any other letter into a question mark, so Hiveku sends the closest name it can keep (accents it can’t store come off, ligatures are spelled out, curly apostrophes are straightened, and digits, symbols and emoji are left out). A one-word name fills both name fields. Each card keeps the name it was saved with, so saving the same card again matches the card already on file instead of adding a second copy. Cards imported from Authorize.Net keep the name Authorize.Net holds for them. See Payments

Project management: statuses that mean what your team means

As of 2026-10-10, every task status says what it counts as: in a project’s settings, Task Statuses gives each status a Counts as choice: To do, Active, Done or Cancelled. Done and Cancelled close a task: it leaves the open counts and is never overdue. A status of your own, such as Placed or Shipped, now closes a task the way Done does. The board, the task panel, open counts, My Tasks, Workspaces and the editor’s Tasks tab all read each project’s own statuses
Removing a status asks where its tasks go: removing statuses, or Reset to Default and Save, asks where their tasks should move, and moves them in the same save. A status that still holds tasks with nowhere to go is not removed
My Tasks shows what you closed in the last 7 days, below your open tasks

Project management: creating and running projects

A new New Project dialog: Name, Description, Type, Status, Priority, Due date and Site, plus a default assignee when you edit a project
As of 2026-10-12, a project created without a type starts as General, whether it is created in the app, through the API, from the phone app or by an AI connection. Before, some of those paths started it as Marketing
The Workflow tab in a project’s settings is now Automations: it lists, in words, the automations that run for the project, and offers two starting points, each created switched off: Have an AI agent work new tasks and Start from scratch
Task triggers start only the runs their settings ask for: a workflow set to start when a task moves into a status no longer starts on every new task
Design and social tasks go to one project you choose: the Design and Social task panels show the project their tasks go into, and anyone who may change projects can pick another with Change. The choice is the whole account’s. The first time, the newest Marketing project is used, or a Marketing & Design project is created
SEO issue tasks go to the project-management board of the site the issue’s page is on

Project management: who may change what

As of 2026-10-12, adding a task needs the permission to add tasks, on the PM page and in Workspaces, as editing and deleting already did. Owners and admins grant it under Settings > Team Members > Manage Roles
Workspaces follows each row’s own account: editing a project or task, or adding a task, from Workspaces needs the permission in the account that owns it. Someone who may only view sees plain values and no add field
AI connections follow the role of the person who created them: adding a task through an AI connection (Claude, ChatGPT, the VS Code extension and the like) needs that person’s permission to add tasks. As of 2026-10-13 the same goes for the rest of the task work: commenting, attaching a file or logging time needs Tasks: Create, changing, completing, claiming or reassigning a task needs Tasks: Edit, and deleting one needs Tasks: Delete. Without it, the connection is told in plain words who can grant it. The default Marketing, Sales, Support and Finance roles have no project-management permissions. Hiveku’s own agents are not affected

Project management: deleting keeps the record

Projects are archived before they are deleted: a project is deleted only once it is archived. AI agents archive projects; a person deletes them, in the app or with their own connection that holds the delete permission. The delete dialog shows the hours logged and the files attached, offers the hours as a CSV, and asks for the project’s name when there are any. Every delete is written to the activity log
As of 2026-10-13, hours a finalized or paid payroll run counted are kept: deleting a project, or a task, whose logged hours a finalized or paid payroll run counted is refused, so the payroll record never loses hours it paid. A bulk delete keeps those tasks and says how many it kept, on the PM page, in the editor’s Tasks tab and through AI connections. Removing a team member keeps those hours too, no longer linked to the person
Each payroll run keeps the list of workspaces it counted: a run remembers the Included workspaces its items were built from, so changing that setting later does not change what an old run counted

Sites

Only a person deletes a site through an AI connection: the connection must belong to a person who holds the permission to delete websites. Connections with no recorded owner cannot delete sites, as they cannot delete projects
A site deletion is recorded: the request is written to the activity log, and each project-management board deleted with the site gets its own entry. A board shared with another workspace, or one holding hours a closed payroll run counted, is kept and unlinked from the site

Moving a project or site to another workspace

A move clears what does not belong in the new workspace: the Slack webhook, the billing client, a Discussion channel that stays behind, people who are not on the new workspace’s team (default assignee, project manager, the team list, section defaults, task assignees and reviewers), and links to a site or SEO project left behind. Both move previews list this in plain sentences, and name the automations that act on the project

Claude Code

A step-by-step setup guide: Set up Claude Code with Hiveku walks through installing the Hiveku plugin in the Claude desktop app or Claude Code, on a Mac or a Windows PC, and connecting one account or many
Plugin 0.27.45 starts its connection to Hiveku through Node.js, the way Claude Code can start it on Windows, and says what each computer needs: Node.js 22.12 or later (or 20.19 or later on Node 20), and Git for Windows on Windows

September 2026

Versions: every change saved, and a way back

As of 2026-09-27, Your site and every branch keep versions: saved copies of your pages you can go back to. Hiveku saves one when you pause, before a step you may want to undo, and when you click Save as a version. Roll back to this version adds a new version that matches an old one, and on Your site can put it live in the same step. Bring back this page puts back one page. See Versions
Undo this turn in the AI chat now goes back to the version saved before the request, and keeps the newer versions. See Undo an AI turn
Project history (formerly Checkpoints) holds restore points for pages, images and data, and can restore Your site to any moment in time. From 2026-10-11, versions replace two automatic restore points: the editor’s every-few-minutes one on every site, and, on sites without a database, the one before each AI request. See Project history

Hosting: the Firewall section keeps your site’s own refusals apart

As of 2026-09-28, Blocked counts only the firewall’s own 403s: a 403 or 429 your site sends itself (a protected page, an expired link, a missing file) is counted apart, shown in a line under the counters and listed under a new Refused by the site filter, and the client detail and the Search engines and ad platforms line split it the same way. Days rolled before 28 September still count those under Blocked. Agents read the same split: site_firewall_get returns totals.siteRefused and takes outcome: 'site_refused'. See Site firewall
Faked ad and inspection crawler names are refused: a client that sends the name of Microsoft’s or Google’s ad checker or inspection tool (for example adidxbot, BingPreview or Google-InspectionTool) from an address those companies do not publish is refused like any unidentified automated client. The real crawlers pass by their published addresses, so ad reviews and URL inspections are unaffected

Forms: choose which forms Hiveku captures

As of 2026-09-24, you choose which of a site’s forms Hiveku captures: Analytics → Forms → Capture has a switch for the whole site, a site type (Marketing site captures every form except the ones you exclude; Web app captures only the forms you choose), Skip sign-in and password forms (on by default, and never applied to a signup that asks for a name), path rules such as /portal/* with a preview of the forms a rule would stop capturing, and Always, Never or Default for each form. Every form shows whether it is captured and why. Changes apply from the next submission with nothing to deploy, and ad conversions waiting to be sent for a newly excluded form are held back
Erase what was captured by mistake: Erase permanently removes the captured submissions your current settings exclude, with their files and form notes and the CRM contacts that exist only because of them, after a preview of the counts. It cannot unsend notification emails or take back conversions already sent to an ad platform
In your site’s code: data-hiveku-capture="off" on a form is now honoured by every Hiveku script, Hiveku Analytics included, and data-hiveku-capture="on" keeps a form on a Web app site. Muting a form’s notifications still stops the email only
AI agents: the Hiveku coding and marketing agents, the Claude Code plugin and Codex can read these settings and preview a change, and are told to save one only after you agree; the Claude Code plugin and Codex also ask for your approval before every change. Erasing stays in the dashboard for now. See Choose which forms Hiveku captures

AI agents: report a problem with Hiveku, or ask for a missing tool

As of 2026-09-24, connected AI agents can tell the Hiveku team when Hiveku gets in their way: Claude Code with the Hiveku plugin, Codex, the VS Code extension, Claude and ChatGPT through an LLM connector, and the department agents you chat with in the dashboard can report a Hiveku tool that fails, or ask for a tool that does not exist yet, and each note gets a reference such as HK-1042. A report carries what the agent saw and the ids of any records involved, never the records themselves; secrets are stripped and email addresses, phone numbers and card numbers are masked on arrival, and only Hiveku staff see it. You hear about a problem only when it changes what you get, and once it is fixed the agent tells you, walks you through any steps and retries the task. Agents that talk to your customers, such as the website chat widget and voice, never file reports. See Reporting Problems to Hiveku

Hosting: the Firewall section, and the evidence behind every row

As of 2026-09-18, every Hiveku-hosted site sits behind an edge firewall: bulk scrapers on known scraper networks are blocked, unknown automated clients are asked to prove they are a browser, and real visitors, search engines, AI assistants, link previews and common uptime monitors pass. Site > Hosting > Firewall shows what was challenged, blocked or rate limited over the last seven days (rolled once a day from the access logs, so today shows tomorrow), the twenty busiest automated clients, and the allowances the site holds. A monitor or an audit tool that identifies itself with a product name can be allowed for the site by that name; an address can be allowed too. Allowing skips the browser check only; volume limits and the network blocks still apply. See Site firewall
As of 2026-09-20, a row opens into its evidence: click a client to see what it actually received (pages served against challenged, blocked and rate limited, bytes, distinct addresses, first and last seen), a per-day table, requests per hour, its most requested paths, the request cadence and a plain-words verdict with the reason. Allow is offered only where it makes sense: a distinctive product token, or an address when the client used at most three; a browser identity shared by every user of that browser gets an explanation instead, and anything else can be reported to Hiveku with the evidence attached. Agents get the same four operations (site_firewall_get, site_firewall_client_get, site_firewall_allow, site_firewall_remove) and the matching routes under /api/olympus/builder/projects/{projectId}/firewall

Content: a named author, the SERP brief, a thesis and five titles, site architecture, bottom-funnel pages, the decision loop, and conversion inside the piece

As of 2026-09-12, a content item carries its structure on the row: eleven new fields every writer accepts and every read returns, author_id (with author { id, name }), faq, answer_block, search_intent, page_type, review_disposition, topic_cluster_id (with topic_cluster { id, pillar_keyword }), cluster_role, page_role, lead_magnet and offer_id, on content_create, content_update, the Olympus and dashboard content routes and the department’s data file, with six new list filters. Six columns are written by their own jobs and read-only everywhere else (400 read_only_field, an echo of what the row holds accepted): the brief route stamps search_intent, page_type, serp_brief and serp_brief_captured_at, the Sunday decay run decay_status, refresh_priority and top_declining_keywords, the publish path refreshed_at. A create or update on a keyword another item already targets answers with a keyword_already_targeted warning and the other item named, never a block, and content_create honours Idempotency-Key so a timed-out retry does not make a second draft. comparison, alternatives and research join the content types
A named author on every post: an account keeps its content authors (GET, POST, PATCH, DELETE /api/olympus/marketing/content-authors, content_authors_*), exactly one of them the default; a publish maps the item’s author, else the default, onto the collection’s author reference and creates the authors entry when missing, so a preset blog no longer fails on its required author field, builds the page’s JSON-LD (Article with the author as a Person, BreadcrumbList, FAQPage from faq) into the collection’s JSON-LD field or onto the row, and regenerates the site’s llms.txt. The check refuses an anonymous post (author_missing) and the department never invents a byline. See A named author on every post
The SERP brief a draft waits for: POST /api/olympus/marketing/content/{id}/brief (content_brief_build) reads the live SERP once, parses the top three pages, decides the intent and the page type by rule with a model tie-break only when the rules cannot separate two, derives the word-count band and what the top three all say, stores the brief as a serp_brief artifact and the SERP in seo_serp_analysis, and stamps the row last; the same build runs for a topic with no item (content_brief_topic). The department builds the brief before the outline, writes Intent: and Type: in its header from the row, answers the people-also-ask questions in faq and the query in a 40 to 60 word answer_block, and refuses to draft to a guess. See The SERP brief
Positioning, a thesis and five titles: the brand positioning (thesis, beliefs, what the brand is against, the category, the proof points with sources) lives on the active brand guide (GET, PUT /api/olympus/marketing/brand/positioning, brand_positioning_get / brand_positioning_set, a full replacement mirrored as a verified knowledge artifact), every draft header carries Thesis: and Hook:, and the rubric gains one sentence a competitor would not publish. POST /api/olympus/marketing/content/{id}/titles (content_titles_generate) asks for five claim-shaped candidates tagged with the sixteen hook patterns and filtered to the stage, titles/pick (content_titles_pick) applies one with a version row, and a Monday job pools Search Console, social (title:<n>) and email (utm_term=title-<n>) numbers into settings.title_results and writes the winner to the meta title when it beats the live title on real volume. The check warns title_generic on a title with no number, name, claim or contrast. See Titles that make a claim
Site architecture: pages and posts carry a role (money, pillar, support, utility; GET, POST /api/olympus/marketing/site-architecture/page-roles, site_page_roles_get / site_page_roles_set, with a seed that proposes roles from the conversion goals, the SEO memory and the route names and never overwrites a role a person set); a content item joins a topic cluster as a pillar or a spoke; a Sunday sweep recomputes each cluster’s coverage, missing subtopics and pillar-link score from published content and maps keyword clusters to the pages that target them; content_site_links returns money pages first and the item’s pillar next with a suggested anchor; and the keyword map (GET /api/olympus/marketing/content/keyword-map, content_keyword_map) shows keyword to item to URL to rank to decay per cluster with every collision. money_link_missing and pillar_link_missing hold the links, keyword_already_targeted the keywords. See Site architecture
Bottom-funnel pages: POST /api/olympus/marketing/content/bofu-plan (content_bofu_plan) plans the brand vs rival, rival alternatives and best category for segment pages from the tracked competitors, the avatars and the brand guide with DataForSEO volume and difficulty (two research calls at most), drops collisions with the item named, and seeds the drafts from three templates with an empty sourced-and-dated comparison table and a decision call to action; the check refuses a rival claim without a source and a date (competitor_claim_unsourced) and a comparison page without a table. See Bottom-funnel pages
The decision loop: every Sunday the content-decay-link run resolves each decaying page to the item that serves it, stamps decay_status, refresh_priority and the declining keywords, raises the new Content Decay Detected workflow trigger once per episode and, when no workflow listens, files a Refresh: title PM task with the pre-filled refresh brief (GET /api/olympus/marketing/content/{id}/refresh-brief, content_refresh_brief_get: what declined, the declining keywords, the SERP brief, the scorecard, the keyword siblings, the newer link donors, a suggested disposition and a checklist, nothing spent). GET /api/olympus/marketing/content/prune-candidates (content_prune_candidates) lists the year-old pages with zero views and zero leads, honest about how each was measured, money pages excluded, with the unpublish named as the default action. The decision is recorded as review_disposition (double_down, refresh, rewrite, consolidate, prune), and the department reads the refresh queue and the prune list before it proposes a net-new topic. See The decision loop
Conversion inside the piece: the brand guide carries its offers (GET, PUT /api/olympus/marketing/brand/offers, brand_offers_get / brand_offers_set: promise, guarantee, bonuses, label, link and the stages each fits, a full replacement with a lock version), a content item names one with offer_id and a lead magnet with lead_magnet, and GET, POST /api/olympus/marketing/content/{id}/conversion (content_conversion_plan) returns the five-stage table keyed to the account’s own journey stage names, the stage row the piece converts on, the offer, the lead magnet with everything it references and the inline, end and upgrade blocks the ::cta{variant=inline}, ::cta{variant=end} and ::upgrade shortcodes render to, ensuring the journey checkpoint that measures the form. The department writes the placements, never the CTA copy, so a changed offer reaches every published piece; the check warns cta_missing and cta_stage_mismatch. On a markdown body the shortcodes publish for the starter’s PostBody renderer; on an html body they are removed at publish until the publish path hands the mapper the plan. See Conversion inside the piece
The pre-publish check gains eleven rules: author_missing, answer_block_missing, faq_schema_mismatch, title_generic, money_link_missing, pillar_link_missing, keyword_already_targeted, comparison_table_missing, competitor_claim_unsourced, cta_missing and cta_stage_mismatch, with the context it was given echoed for a local re-run. See Pre-Publish SEO Check, The Content Department and the Content API
Polish, 2026-09-12: the refresh queue in one call, and a source on every indexed passage: content_list and the dashboard content list take decay_status (decaying, recovered or none, a state rather than a raw status; anything else is a 400 naming the list) and sort=refresh_priority, so content_list({ status: "published", decay_status: "decaying", sort: "refresh_priority" }) is the whole refresh queue, paginated on the same predicate; kb_documents_index_text (POST /api/olympus/marketing/knowledge-bases/{kbId}/documents) now stores source_url (normalised, as metadata.url, so a research run finds the page already indexed and a search hit cites it) and tags instead of dropping them; the lead magnet kind is one eight-value list (guide, checklist, template, ebook, whitepaper, webinar, download, other) on the routes, the editor picker and the conversion plan, which keeps a stored download or other instead of calling it a guide; a cannibalisation finding a person moved to in_progress still counts as open in the prune list and the refresh brief; the dashboard editor writes a version only when the body changed or the save asked for one; and the content routes’ error hints name the real tools (content_authors_list, brand_offers_get, the dashboard forms list). See List Content and Knowledge Documents

Content: distribution on every piece, leads per piece, proof you can cite, and research that stays

As of 2026-09-12, distribution is part of the asset: a content item carries a distribution plan from brief time under settings.distribution_plan (owned email first, then the social, community, partner, outreach and paid channels the piece’s stage and type call for, each row with a format, a status and, once it exists, the derivative it produced), written by the Content department in the same call as the copy and read by its new Channels: header line. Every native publish fires one content.published event, and the new Content Published workflow trigger carries the live URL, whether the page is live yet and whether it is the first publish, with filters on project, content type and first publish only. Two templates run the first two channels: Content Published to Social Drafts (content-published-repurpose) drafts three posts per first publish for approval, and Weekly Content Digest Newsletter (content-digest-weekly) drafts a Tuesday digest of the week’s pieces and sends it only after a named approver says so. Every derivative link now carries utm_medium=content and utm_content=<slug>, the keys the attribution resolver reads, so a click on a repurposed post finally credits the piece; the links said utm_medium=social before and credited nothing. A publish with no plan is said out loud by the department and the editor, never blocked
Leads per piece: the content list gains a Leads column and sort (the forms-ledger count for the page, with the lead rate in the tooltip, an em dash when the collector could not answer), the editor’s sidebar a Performance section (views, visitors, form submits, leads, contacts, deals, rank, the linked social posts and the lead rate over 7, 30 or 90 days or all time), and content_analytics its first writer: a nightly job stores one row per closed day per published piece with the rolling scorecard in its envelope. content_analytics_get and GET /api/olympus/marketing/content/{id}/analytics answer from the same module instead of zeros, the batch views route returns form_submits and leads beside views, and GET /api/olympus/marketing/reports/campaign-roi gives the department the same per-asset contacts, deals and revenue the Reports hub shows, content items included
Proof you can cite: GET /api/olympus/marketing/content/proof-pack reads the account’s public testimonials, review text, the first message of support tickets in the segment, call summaries, survey free text, measured before/after grid results and the objection library in one call, each entry with its source, a ready-made [source: <label>:<id>] citation the pre-publish check accepts, and a consent flag that says whether it may be quoted verbatim. The check gains two proof rules: a figure with no source is an error at the decision stage, and a consideration or decision piece needs a proof element under every H2. POST /api/olympus/marketing/content/case-study drafts a case study from a won deal (the customer’s words from tickets and calls, the consented testimonial verbatim, the numbers parsed from the grid and never from the model) as a draft the editor opens with its five case-study sections; a deal that is not won or a testimonial without consent is refused and nothing is written
Research that stays: POST /api/olympus/marketing/content/{id}/research searches every knowledge base in the account, reads the SERP, fetches the web pages it needs, extracts claims each with a verbatim quote and a source URL, indexes every page it used into a per-account Content research knowledge base with its URL, writes the brief as a knowledge artifact that kb_search can find, and stamps settings.research on the item last; a re-run refreshes the same artifact and never re-indexes a page the KB holds. The same run works for a topic with no item yet, and GET /api/olympus/knowledge-bases/artifacts lists every research, SERP brief, positioning, proof pack, case study and data study artifact by type without knowing the knowledge base first. The department searches before it writes, runs the research when the item has none or it is older than 30 days, cites each claim’s source inline and reports Sources: n in its header. See Distribution, Performance, Proof and Research, Pre-Publish SEO Check and the Content API

Images: GPT Image 2.5 by default, the brand image profile, and article images in one step

As of 2026-09-12, GPT Image 2.5 draws the pictures: every image surface (the Media Library’s generate action, the Design Studio chat, the Generate Image and Image Set workflow nodes, the Visual Editor, article images, the agents, the Claude Code plugin and the API) now defaults to OpenAI’s gpt-image-2.5-flare, released 2026-09-08: better than the previous default at about half the latency, with stronger preservation of a referenced subject on edits. A failure on that lane renders the same request on Gemini 3.1 and the result says which model drew it; Gemini 3.1 and GPT 5.4 stay selectable, gpt-image-2.5-sunburst is the premium pick for an edit that must hold the subject exactly, and the six GPT Image quality settings (low, medium, high, xhigh, max, auto) are accepted where a quality is asked for. Each image is charged to the credit ledger at what it actually cost
The brand image profile: a branded generation used to be told the brand name, three colors, two fonts and 200 characters of voice. It is now handed the whole imagery side of the brand guide as plain sentences (personality and adjectives, the full palette with hex codes and gradients, typography for any text in the image, photography, illustration and icon style and rules, logo rules, the AI prompt rules and an avoid list) plus the primary logo and up to three Media Library images tagged brand_reference as reference input, with the prompt told which attached picture is which. Results carry brand_reference_ids and name any reference that could not be fetched; GET /api/olympus/marketing/brand/image-profile (brand_image_profile_get) returns the profile exactly as a model receives it. The flux, flux-pro and recraft models take the written profile only
Mark approved brand imagery with one tag: add brand_reference to a Media Library image under Marketing > Media (or with tags on the media API) and it rides along with the logo on every branded generation from then on. The three most recently tagged images are used; tag a newer one to promote it
Article images: a content item gets a hero and one image under each major section where a picture adds information, from one step that reads the stored body, the item’s grounding and the brand image profile, renders the hero first and the sections with the hero as a reference so the set matches, registers each in the Media Library (tags content_image and content:<item id>), places each under its heading and sets the featured image with its alt text. Available as Generate images in the marketing content editor (it opens with what the run would do and how many generations are left), as GET and POST /api/olympus/marketing/content/{id}/images and their dashboard twins, as the content_images_generate tool for the department, the Claude Code plugin and the VS Code extension, and as a Generate images switch (off by default) with a Max images cap on the Create Marketing Content workflow node, which the shipped Weekly Trending Topic Blog Draft template turns on so the Monday draft arrives with its pictures and the count in its email. Each image draws from the monthly image allowance; a run refuses with 402 quota_exhausted before planning when nothing is left, stops with a partial result and a warning when the allowance runs out part-way, and refunds a render that fails. Alt text is written for every image and checked by the pre-publish check. The plugin’s content play now illustrates every long-form piece this way after the draft and before the quality gate, with the allowance read first. See Media Library and AI Images, Images for the piece and Article Images

Content: grounded drafts, a pre-publish check, real internal links, and a calendar that shows what will publish

As of 2026-09-11, Foundation first: the Content department reads the account’s customer avatars, journey maps, before/after grids, brand guide and existing content before any outline or draft, and every draft opens with one header line: For: avatar | Stage: journey stage | Promise: before/after item | Keyword: target keyword | Links: n internal links. No usable avatar means no draft; the department names the missing fields and points at the Customer Avatars page instead of writing generic copy. The brand file it reads now carries ai_forbidden_phrases, copy_dos, copy_donts and the reading level, a forbidden phrase is a hard fail it rewrites rather than saves, and long-form copy runs through a four-rule rubric (sourced claims, no filler openers, one job per section, a call to action matched to the stage). The target keyword travels with the item in its target_keyword column (mirrored to settings.target_keyword for older readers), which the editor’s new Target keyword field, the pre-publish check and rank tracking all read
As of 2026-09-11, Who this is for, recorded on the item: a content item now carries who it is written for as five typed fields, avatar_id, journey_id, journey_stage, before_after_grid_id and target_keyword, and every reader returns them with customer_avatar, customer_journey and before_after_grid as { id, name }. The marketing editor’s sidebar gains a Who this is for panel (avatar, journey and stage, before/after grid, target keyword, with a one-line summary and Clear), the New dialog offers the avatar and stage so a row starts with its audience, and the AI assistant on the item reads the five as its context instead of asking for the audience in every chat. content_create, content_update, the Olympus and dashboard content routes and the Create Marketing Content workflow node accept the same five; an id from another account is a 400 invalid_reference that writes nothing, and the Olympus list filters on avatar_id, journey_id, before_after_grid_id and journey_stage so the avatar-by-stage coverage matrix is one call per cell. The Content department records the avatar, stage, grid and keyword it drafted for on the row and reads its header line back from them; the workflow node warns on the run log when a draft is written for nobody while the account has avatars; and the Claude Code plugin and VS Code extension write the five with the draft and treat an echo without them as a write that did not land. See Who this is for
A pre-publish SEO check on every surface: one deterministic check runs on the marketing editor (a Pre-publish check section above Status with a score, errors under Fix before publishing and warnings under Worth a look, each row jumping to its field), on GET /api/olympus/marketing/content/:id/seo-check and its dashboard twin, on the content_seo_check MCP tool, and inside content_publish_to_site, which returns the findings as warnings[] plus a structured seo_check. It checks meta title and description lengths, the placeholder slug, an empty or thin body, multiple H1s, keyword placement in the title, slug, H1 and first 100 words, heading order, alt text on the hero and every inline image, internal-link count, figures with no source link, and the brand guide’s forbidden phrases. It never blocks: errors ask Publish anyway? in the editor and come back as warnings on the API
Internal links from real URLs: content_list and content_get carry url (and url_source) for every published, site-linked item, the department’s data file carries the same, and GET /api/olympus/marketing/content/site-links?project_id= (content_site_links) lists every published post and page on a project with its live URL and explains every omission in notes. The department links at least two existing pieces by URL from that data and says Links: 0 or Links: 1 when fewer exist, rather than inventing a path
Scheduling that executes: a scheduled content item now lands on the CMS scheduler that runs, whether scheduled from the editor’s new Schedule dialog (with the deploy targets the scheduler executes), PUT /api/marketing/content/{id}, the Olympus schedule routes or the content_schedule tool. An item not linked to a site collection cannot be scheduled and answers 409 not_linked with the link step named; a linked item with no site entry gets one created as a draft so nothing goes live early; and when the schedule runs, the item is stamped published and its mirror date cleared. On the dashboard save, only a changed future time is a schedule request, null never cancels, and cancel_scheduled_publish: true does
The content calendar: Marketing > Content > Calendar is a month grid and a list of what is scheduled, published, failed or merely recorded (a date on an item that nothing executes, said plainly), with the account’s cadence in the header: published in the last 30 days, scheduled, failed publishes needing attention, and the target cadence read from the department’s memory when one is written there. Fed by GET /api/marketing/content/calendar?from=&to=
Resume a department turn: talk_to_department waits about 110 seconds while a department turn may run for 1200; a timeout now returns session_id, turn_id and whatever had arrived, and GET /api/olympus/marketing/ai/turns/:turnId (department_turn_get) polls the turn under the same API key, with since_seq paging, a stale flag for a dead worker, and the finished shape (response, tool_calls, data_updates) once it completes
Fixed on the way: the Trending Topics to Blog workflow node saved empty article bodies since April because it posted body where the route read content; both names are accepted and the node fails when the saved article is empty. Site posts born from the New Content modal published at the untitled-content slug; the slug is now derived from the first real title. Unpublish in the editor set the status back to published; it sticks. The sidebar said Live on your site before any deploy; it is keyed on the recorded deploy outcome. content_create and content_update declare every parameter the routes read, so featured_image_alt, meta_keywords, canonical_url, settings and the CMS link no longer fall off between an agent and the row. See The Content Department, Pre-Publish SEO Check and Scheduling and the Content Calendar

Webflow: the content-source switch, and every write pair asks on both halves

As of 2026-09-10, 111 actions: project_cms_provider_set joins the Webflow registry as its one Hiveku-side action. It switches a project’s content source between the Hiveku CMS and the Webflow CMS with the same bound-site check as the Settings page, so a chat or an MCP client can finish the step that used to need the dashboard. The workflow palette gains the matching node under a new Project family (95 generated nodes beside the sixteen featured ones) and the MCP server its 111th webflow_* tool
The content source is not switched for you: a Webflow-hosted site keeps the Hiveku CMS as its content source until you switch it. The Content department and the AI now say so and will not publish a content item to the site until the source is Webflow CMS; they offer the switch, which asks before it runs. Page SEO, schema markup, assets, custom code and publishing work either way. The CMS capabilities read now carries external_platform and project_type beside provider, because provider names the content source and not the host
32 confirmation gates, direction irrelevant: the gate rule now covers a write that cannot be undone through the API, one that changes what a visitor sees or what is collected about them, and one that starts or stops delivery of customer data to a third party, and where the OFF half of a pair asks, the ON half asks too. Thirteen writes joined the nineteen already gated (the deletes, order fulfil and refund, robots.txt replace, webhook update and the site publish): item publish and unpublish, the site and page script lists, the Google tag, the Hiveku snippet, llms.txt, robots.txt merge, redirect create, well-known create, webhook create and the content-source switch. Nothing was ungated. The workflow nodes carry the checkbox, the MCP tools the confirm argument, and the Claude Code plugin asks before each one
One notice for page wording: the single-language notice reads the same on every surface: “These words are edited in the Webflow Designer. Page titles, slugs, SEO fields and CMS content stay editable in Hiveku. Webflow only opens page wording to other tools on a site that publishes in a second language.” See The Webflow AI Chat, Webflow as the Content Source and Webflow for Developers

Webflow: keep the site in Webflow, run it from Hiveku

Connect once: authorize a Webflow Data Client app over OAuth and pick which sites to share on Webflow’s own consent screen, or paste a site API token. The connection is an account default that every project inherits, with a per-project override for agencies running several Webflow accounts in one workspace. Tokens are encrypted at rest and never echoed back, and a pasted token is validated against Webflow before anything is stored
A site token is the lesser option, and we say which parts it loses: it covers CMS, assets, forms, comments, ecommerce, page metadata and publishing, but Webflow refuses it custom code and webhook registration. No webhooks means no inbound events and no form routing, so fifteen actions answer 412 oauth_required on a site token rather than failing upstream as an unexplained 403
The Webflow workspace: a full screen at /<accountId>/dashboard/<projectId>/webflow with 27 routes across sixteen rail areas — overview, pages and a page editor, CMS collections, fields and items, assets, SEO, forms, comments, components, ecommerce, custom code, redirects and robots, webhooks, departments, activity, publish and settings. No area is hidden by what your plan or credential can do; every page explains its own limit instead
A chat that drives the site: a collapsible AI pane on the left of the workspace, locked to Webflow mode because the site has no Hiveku code to write. Ask it to draft posts into a collection, rewrite every page’s SEO title and description, add a Google tag or publish, and it calls the same operations the panels call, behind the same gates
111 actions, one registry, three surfaces: the workspace panels, 111 workflow action nodes and the webflow_* MCP tools all run the same registry over the Webflow Data API v2, nine of them served by Webflow’s beta namespace. A person, an automation and the AI therefore pass the same permission, confirmation and locale gates and land in the same audit log
Webflow as the content source: switch a project’s content source and New Content, the Content department, the AI and the CMS panel write Webflow collections instead of Hiveku’s own. Saving an entry stages it in Webflow; Publish makes it live. The SEO department’s page-SEO apply reports applied_via: webflow with publish_required: true, so a report never claims a change is live before the site is published
Forms, comments and events flow back in: an inbound receiver verifies each delivery — Webflow’s HMAC signature plus a per-connection URL secret on an OAuth connection, the URL secret alone on a site token — records it once per site and event, routes form submissions into the Hiveku Forms ledger, the CRM contact and notifications, and feeds 13 workflow trigger nodes covering site publishes, CMS item lifecycle, page creation and deletion, page metadata changes, new comments and form submissions
Analytics without a Designer trip: install the Hiveku analytics snippet on a connected site from the Custom code panel, on an OAuth connection. It is registered as an inline script applied site-wide and starts counting after the next site publish; a site-token connection gets the tag to paste into Webflow instead
Kept honest in the background: four crons watch the connection — token health, webhook health, webhook URL reconciliation and event retention — and a connection made before webhook registration existed can be brought up to date from Settings without reconnecting
The limit, stated plainly: Webflow’s Data API cannot write page or component body text in a site’s primary locale, cannot create, delete or rename pages, and cannot touch layout, classes, styles, interactions or components. Those stay in the Webflow Designer, and the workspace says so on the page rather than hiding the control. What is editable from Hiveku: everything bound to a CMS collection in either locale, page titles and slugs, SEO and Open Graph, JSON-LD, assets and alt text, custom code and scripts, form submissions, comments, ecommerce, and publishing. Page titles and SEO are editable in the primary locale; adding a secondary locale unlocks page and component body text in that locale only
Enterprise-plan sites additionally get 301 redirects, robots.txt, llms.txt, files under /.well-known/ and the Webflow site activity log; on other plans those actions decline with the plan named
See Webflow Overview, Connecting Webflow, The Webflow Workspace, Webflow as the Content Source, The Webflow AI Chat, Webflow Automations and Webflow for Developers

Creative Studio: brand-aware images, a media toolkit, and fonts that survive export

Brand by default: every AI image generation now applies the account’s active brand guide unless you opt out, in chat, with the Apply Brand Context setting on the Generate Image, Image Set and Video workflow nodes, or with use_brand: false on the API. The result records whether the brand actually reached the model; with no active guide it says the image is unbranded, and a brand guide that cannot be read refuses the generation before anything is spent instead of billing an unbranded render
Image allowance read: before a batch, an assistant can read what the account has used, its limit, what remains and when the period resets, from the same counter the next generation is gated on. Generations and upscales draw from it; imports, transforms and design exports do not
Import, transform, upscale: import an outside image by URL as a real copy in your storage (25 MB, images only); crop, resize or re-encode an existing asset for free; AI-upscale up to 4x within a 32 megapixel cap for one image generation plus $0.03 per output megapixel. Every operation creates a new asset linked to the original; an asset’s bytes, dimensions and generation metadata can no longer be rewritten, only its title, alt text, caption, description, tags and folder
Custom brand fonts render in exports: PNG and MP4 exports, save-to-library and the final storyboard render now carry the brand kit’s custom fonts. A font that fails to load falls back and the export names it in a warning, never a failed render
The inbox hears the studio: a comment pinned on a design files an item in the Ops Inbox (one per thread), and a storyboard video reaching completed or failed files one item per run, each with a link to the design
Creative to a scheduled post: an assistant working through the Claude Code plugin or the API can attach a finished design export or library asset to an existing or scheduled post, replacing its media list wholesale with a type per file; publishing and published posts stay locked
Six wide-format templates: two 1200 x 600 email headers, a 1200 x 630 Open Graph card, a 1280 x 720 YouTube thumbnail, a 1584 x 396 LinkedIn banner and a 1500 x 500 X header, brand-substituted and grouped under their sizes in the Templates library
Concurrent edits cannot clobber each other: the canvas carries a version on every save, whether you, a teammate or the AI designer wrote it. A save built on an older version is refused; the editor asks whether to keep your version or load theirs, and the AI designer re-reads and re-applies your request instead of overwriting. Clip requests now report the length that was rendered next to the length that was asked for, since several video models snap to fixed steps. See Media Library and AI Images, Brand fonts in exports and Sized templates

File uploads on website forms

Nothing to wire: add <input type="file" name="resume"> to any form on a deployed site and the file uploads to Hiveku when the visitor picks it, with a status line under the input and a submit button that waits for the upload. No upload endpoint, no storage to provision, no per-project database
Files travel with the lead: download links in Analytics → Forms, real attachments on the notification email (up to 5 files or 25 MB per email), an Attachments section on the CRM contact plus document links on the form activity card, and {{trigger.attachments}} in workflows with an Attach form files toggle on the Send Email node
Limits and controls: 25 MB per file by default, adjustable per project from 1 MB to 100 MB (files over 10 MB upload in parts automatically), 5 files per submission by default, documents and images only, with the file type verified against its contents before anything is stored. Per project you can switch uploads off, narrow the accepted types, raise or lower the size limit and set retention (one year by default, 30 days to one year) under Forms → Notifications → Uploads. Opt a form or input out with data-hiveku-uploads="off"
Malware scanning: every uploaded file is scanned after it lands. A file becomes downloadable once its scan is clean, usually within minutes; the notification email waits up to 10 minutes for the verdict before going out without the file; a file the scanner could not read is delivered with a “Could not be scanned” note, and a flagged file is removed and shown as “Removed: malware detected”
Open attachments from the iOS app: tapping a form attachment on a contact’s timeline opens it through a short-lived link, and the contact screen lists every file the contact sent
Agents and tools: the coding agent, the Claude Code plugin and the VS Code extension know the rule (a file field is a named file input, nothing else) and gain marketing_form_attachments_list, marketing_form_attachment_download_url and the form upload settings tools, on the coding agent, the marketing agent, the Claude Code plugin and the VS Code extension alike. See File uploads

Working branches in the editor

Branch selector: pick the branch you are working on from the top left of the editor. The file tree, live preview, AI chat and Database panel follow it, and edits from a chat turn land on that branch, never on main
Uncommitted and committed: saves land on the branch immediately; Commit changes records a named point. Deploys, pull request merges, branch creation and branch deletion commit your unsaved changes first so nothing is lost
Environments: Development and Staging can serve a branch; Production always serves main. The Deploy button knows which branch each tier ships, and the Environments strip on the Branches tab shows what each tier is serving and since when
Pull requests: open, review with a per-file diff, and merge into main. Merges are strict: any conflict means nothing is merged, and the conflicting files are listed so you can resolve them on the branch
Branch previews start automatically when you switch and stop after an hour idle; a Stop preview action lives in the branch menu
One database per project: the Database panel says so plainly on a branch. Content and visual editing stay on main for now
Claude Code and VS Code: the file tools take a branch parameter, project_vcs_commit with no files commits a branch’s pending changes, project_vcs_diff_file returns one file’s diff between two branches, and project_vcs_env_bindings tells deploy_site what ships. The VS Code extension gains pull request file review and reopen, binding-aware deploy labels, a branch item in the status bar, and a command to stop a branch preview. See Branches, environments and pull requests

August 2026

Accounts can no longer be deleted out from under the people who live in them

Home accounts explained: every login is anchored to one account, set when the profile is first created. Being invited elsewhere adds access without moving it, so a personal workspace you signed up with can still be your home account long after your real work moved on. See Your Home Account
Deleting an account is now blocked when it is the home account of someone who also belongs to other accounts. Previously that deletion removed the person entirely and took their access to every other account with them, and removing them from the team first did not prevent it
Profiles can be moved to a different account on request, with one condition: the person must already be a member of the account they are moving to. Their memberships are unchanged by the move. Email support@hiveku.com with the person’s email address and the destination account
Deleting or offboarding an account now revokes its MCP credentials immediately, so editor and CLI access stops at offboarding rather than lingering until the final purge

PPC depth tools on every platform

Google Ads extended lane: geo, radius, and language targeting (including the presence setting that stops local budgets leaking to out-of-area searchers), conversion-action create/update with the tag snippets to install, image and YouTube asset uploads, rule-based remarketing lists, shared negative keyword lists, and full Performance Max asset-group support — one atomic create that refuses to build a group that can never serve, per-group servability diagnostics, and a performance read with Google’s per-channel split of where PMax delivery actually went
Microsoft Advertising family: campaign build-out, the full targeting-criterion surface (locations, radius, location intent, dayparting, device, demographics), audience association, UET tags and conversion goals with a plain-language readiness verdict, sitelink and callout extensions, shared negative lists, and three account reports — search terms with a wasted-spend summary, quality score with the weak components named, and impression share split into budget-limited vs rank-limited headroom
Meta and LinkedIn depth: Meta breakdown insights, creative and audience management, lead retrieval, Advantage+ support, and confirm-gated audience edits; LinkedIn’s demographics report (performance by job title, seniority, industry), campaign groups, creative lifecycle, conversion rules and API events, matched audiences, and ABM company segments
Disapproval reads on all four platforms return the same shape, with policy reasons where the platform provides them — a disapproved ad spends nothing and silently starves its campaign, so these are the first reads to run when traffic drops
Budget guardrail per ad connection: set a monthly spend target and a daily sweep watches it — an alert files to the agent inbox at a configurable percent of target (default 85), and an opt-in hard line auto-pauses live campaigns
Creations land inert by design — paused on Google, Meta, and Microsoft, drafts on LinkedIn — and anything that spends, changes live delivery, or is irreversible previews first and executes only on an explicit confirm. See PPC Depth Tools

SEO delivery: live rank tracking, page intelligence, and the Tag Manager pipeline

Live rank tracker: track a keyword and the first check runs within minutes — Google and Bing positions, local-pack tracking by business name and city, and AI-engine citation tracking across ChatGPT, Perplexity, AI Overviews, Claude, and Gemini, with per-keyword history views
Page intelligence: Core Web Vitals with real-user field data and a Lighthouse lab run in one call (works on competitors too), a Knowledge Graph entity check, a five-section conversion audit of any landing page with named fixes, and a citation audit that diffs the business’s public listings against its canonical name, address, and phone
Analysis suite with honest data-source notes: content decay, keyword cannibalization, internal-link graph, E-E-A-T scores, and 30-day ranking forecasts — each names exactly where its data comes from and when it’s empty, instead of implying analysis that didn’t happen
Search Console, full scope: the canonical multi-dimension analytics query, time series, period comparison with winners and losers, URL inspection, an index-coverage substitute, and sitemap submit/delete — connections authorized read-only before late August need a one-time reconnect for sitemap writes
Google Tag Manager pipeline: create a tag as a workspace draft, snapshot it into a version, and publish — with the publish step confirm-gated because it changes the client’s live site. Closes the classic failure of conversion tags that sat unpublished recording nothing. See SEO Delivery Tools

Client reports and the two-key approval rail

Client report lifecycle: create a scheduled, shareable marketing or social report, regenerate its stored numbers on demand, fetch the public share link, email it to the client behind a recipient-list preview and confirm, or download the marketing report as a PDF of the exact stored numbers
Report sections cover leads, deals won, traffic, spend, SEO, rankings movement, search-term wins, listings, AEO, local, and a work log showing the client what was done
Implement-with-AI rail: an SEO finding filed as a task can be handed to the coder agent headlessly — it edits the website project, typechecks, test-builds, and stages the production deploy for approval. Two keys stand between a finding and the live site: one confirm to dispatch the work, a separate approval to ship it
Approval rail and agent inbox: list, inspect, approve (confirm-gated, single-use tokens), or reject staged agent actions; the agent inbox is the staged alert queue where guardrail findings and health sweeps land, with resolve-or-dismiss lifecycle. See Client Reporting & Approvals

Standing marketing playbooks

Thirteen ready-made workflow templates for recurring hygiene: weekly search-terms negatives mining on Google and Microsoft, monthly impression-share review, lost-backlink alerts, monthly tech-audit regression diffs, content-decay refresh briefs, monthly AEO visibility, a weekly Core Web Vitals watch, daily review-SLA escalation, weekly Business Profile post drafts, and event-driven responses to ad disapprovals, rank drops, and new negative reviews
Every template is staged-to-approval: negatives and review replies land in the ops inbox as drafts, posts land in the composer approval queue, and read-only loops just alert — nothing is applied, posted, or published automatically
Three named delivery playbooks — the weekly PPC optimization pass, the monthly SEO retainer, and the monthly AEO pass — give the agent the ordered tool sequence, expectations, and gotchas for each recurring deliverable. See Standing Playbooks

Call tracking: keyword-level attribution and every-platform conversion send-back

Keyword and ad-group attribution: calls from Google Ads clicks now resolve to the exact campaign, ad group, keyword, and ad automatically — shown on the CRM contact timeline, in new by-keyword and by-ad-group breakdowns on Analytics → Calls and the Attribution dashboard, and in a Calls-by-keyword table on each PPC campaign page
Conversion uploads to Microsoft Advertising and Meta join Google Ads and GA4: one toggle sends qualifying calls to every connected ad platform, with per-call upload status chips on the call drawer so a disconnected account can never silently stop your conversions. Default policy is now Answered calls only
Exact PPC call counts: campaign call numbers join on the platform’s own campaign ID, so renames and UTM changes no longer zero them out
Smarter number pools: numbers recycle after a two-day post-call hold instead of a month, repeat callers within 90 days still attribute to their original campaign (with a repeat-caller badge), and search-engine crawlers no longer consume tracking numbers or see swapped ones
Automatic monitoring: admins are emailed when a pool runs out of numbers or when a site’s tracking script goes missing — each email names the problem and the fix
Honest reporting: unattributable calls show as Unmatched instead of inflating Direct traffic, truncated views say so, and the calls CSV export carries the full attribution columns
Cost-per-lead report: a new Reports tab computing spend against credited leads under five attribution models (first-touch, last-touch, 50/50 split, W-shaped, qualified), down to ad-group and keyword depth, with tracked calls counted as touches alongside forms
Conversation keywords: define the terms that matter and every call transcript is scanned automatically - chips on the call log, trend charts on Analytics, and workflow triggers that fire when a call mentions them
Local numbers for every visitor: pools now show visitors a tracking number with an area code local to them, and the Pools page shows each pool’s area-code spread
Route by caller location: numbers can send callers to different destinations by their area code, and ring-group round robin now takes true turns
Form and deal conversions upload to Microsoft Advertising and Meta alongside Google Ads
See Phone Tracking and the new Migrate from CallRail guide

Client portal and payment pages overhaul

Payment pages: shareable “pay us any amount” checkout at /pay-to/your-slug. Fixed, preset, or open amounts, reorderable payer fields, optional tax with tax-exemption claims, a customizable thank-you page or redirect, a branded payer confirmation email with test-send, CRM automations (auto-link the payer’s company, optionally create a deal), an outbound webhook with a test button, and per-page views/conversion/revenue analytics. Every payment lands as a normal invoice and payment record. See Payment Pages
Your own billing domain: connect billing.youragency.com from Commerce > Settings > DNS with two DNS records; SSL issues automatically and every share link and portal email switches over. Domains are re-checked hourly and certificates self-repair. See Billing Custom Domain
Portal settings redesigned: a dedicated page with sections for contacts, permissions, appearance, emails, and advanced controls, live previews of the portal and its emails, and every field showing the value the portal actually renders
Appearance controls: brand color, header style, welcome copy with merge tags, an editable help block, support contacts, and Terms/Privacy links in the portal footer
Members area: clients see who at their company can use the portal, edit contact details, and portal admins add or remove members. Changing a sign-in email requires verifying both the old and the new address (on by default)
Saved-card editing: clients update a card’s expiry date and billing address themselves; the card number and security code are never stored or editable (on by default)
Contracts in the portal: clients open a contract, see signer status, sign when it is their turn, and download the completed PDF

Domains: buy, transfer and manage

New Settings > Domains page. Every domain your account uses in one place, across all sites and environments. Domains you connected previously appear automatically
Buy a domain without leaving Hiveku. Live availability across .com, .net, .org, .co, .io, .shop and .agency, filter by extension, sort by price, and pick a term from 1 to 10 years
Registration and renewal prices are both shown before you pay. A promotional first year is common across the industry, so we fetch the real renewal figure rather than assuming it matches, and say so plainly when a particular name’s renewal price cannot be read
Transfer a domain in from GoDaddy, Namecheap or anywhere else. We read the registry first and tell you which situation you are in: a domain whose DNS is hosted elsewhere transfers with no effect on your website or email at all, and one using its registrar’s own nameservers has its DNS set up here first, because those nameservers stop answering once that registrar is no longer in charge
Transfers are blocked, not warned about, when proceeding would cost you something. A domain renewed in the last 45 days gains no time from a transfer while still costing a full year, so we refuse rather than let you pay for nothing
Your authorisation code is encrypted the moment you paste it and never shown again
DNS report on any domain, connected to Hiveku or not. Where its DNS actually lives, whether its email records are intact, and whether a certificate authority restriction would block HTTPS. Read-only, changes nothing, and names its own blind spots rather than implying it saw everything
Automatic renewals with reminders at 35, 28, 21, 14, 7 and 3 days before expiry. Expiry takes a website and its email down on the same day, so the ladder starts early
Hiveku is a reseller, and the page says so. Domains are registered through our accredited registrar partner, who appears in your public WHOIS record, and the emails you receive from them are genuine
See Domains, Buying a Domain and Transferring a Domain In

Sensitive (write-only) environment variables

New Sensitive toggle on any environment variable. Once saved, the value is hidden everywhere in Hiveku and cannot be revealed again, by you, by teammates, by Hiveku staff, by AI agents and the MCP tools, or by the VS Code extension and hiveku-sync
Builds and deployments still receive the real value. Only the ability to read it back through Hiveku goes away
Values cannot be un-hidden, because nobody can retrieve them to show you. Use Replace value to set a new one, or untick Sensitive while supplying a replacement to make the variable readable again
The AI agent can create, update, delete and mark variables sensitive, but cannot read a sensitive value. It reports such a variable as configured rather than missing, so it will not loop trying to set one you already have
hiveku-sync pull-env and the VS Code extension list which variables they skipped, so a local .env.local is never silently incomplete
Sensitive values are stripped from stored build logs, which are readable through the dashboard and the deployment-log tools
Marking a variable sensitive does not retroactively un-leak it. Rotate anything that may already be exposed. See Environment Variables

Environment Variables editor rebuilt

Renaming a variable, or changing which environments it applies to, no longer leaves a duplicate behind. Previously the old entry survived and reappeared on reload
Edits are staged and applied together when you click Save changes, with a summary of what will be added, updated and removed. Deletions show an Undo link and are not applied until you save
Deleting a variable used to report success even when the delete had failed. Deletion is now applied atomically with the rest of your changes
Variable names are normalised to uppercase as you type, so my key and MY_KEY can no longer become two separate entries that look identical
Duplicate names, reserved platform names, and invalid formats are flagged inline on the offending row before you save, instead of failing after a round trip
New Import for pasting a .env file. Handles comments, export prefixes, quoted values and values containing =, and reports unparseable lines instead of skipping them silently
Concurrent edits are detected. If a teammate or the AI agent changed a variable while you had the page open, saving stops and names the conflict rather than overwriting their work
All of a project’s variables are capped at 60KB, with a warning before you save rather than an opaque error after
The editor now has its own Environment Variables page. Project Settings shows a read only summary with a Manage link, and never displays values

Security fixes

Branch and pull-request previews were being given production environment values. They now correctly receive development values. If a variable is scoped only to Production, add a Development or All Environments value for it so previews still work
Real .env files are no longer included when a project is exported to GitHub. .env.example templates are still exported

August 2026

Number porting

Bring your existing numbers to Hiveku — a full-page wizard at Communications → Porting → New port request runs a free portability check with a per-number verdict (portable, FastPort eligible, SMS-capable, or not portable with the reason) before anything is committed. Bulk-paste tolerant of spreadsheet exports, up to 100 numbers per request
Guided port-away paths for CallRail, GoHighLevel, and Twilio — step-by-step instructions, a copy-paste support-ticket template, and per-provider gotchas — plus a generic path for any other carrier
Letter of Authorization e-sign — Hiveku prefills the LOA, the authorized person signs it in the browser via an emailed link (or on the spot), and the signed copy attaches to the port automatically. Already have a signed LOA? Upload it instead
Every port gets an order page with a PORT-XXXXXX reference tracking the full pipeline — filed → sent to carrier → transfer date confirmed → transferred — plus a carrier-requirements checklist before you send, plain-language exception fixes with one-click resubmit, mid-flight carrier-detail updates (for providers that supply the account number and PIN after filing), and a carrier comment thread
Client handoff for agencies — a secure no-login link where the account holder enters the account number and PIN, uploads a recent bill, and signs the authorization, so you never need the client’s provider login
Account admins get in-app and email updates at every step, and freshly ported numbers land on the Numbers tab marked Needs setup — assign E911, activate, and choose where calls ring. See Number Porting

Call tracking: repeat callers, faster recycling, and the swap tester

Repeat-caller matching — a caller who comes back within 90 days is matched to their original campaign and badged as a repeat caller on the CRM timeline, even after their tracking number was recycled to a new visitor
Numbers recycle far faster: a number is held just two days after a call instead of a month, so a small pool now covers much more traffic
Watch it swap opens your live site in a popup with an on-page verdict banner proving the swap; Test my live site runs full diagnostics — script detected, swappable numbers found, a real test assignment, and live pool availability
Google Ads attribution now resolves down to campaign, ad group and keyword on each call record
Optional GA4 send-back posts a phone_call event for qualifying tracked calls to your Analytics property, joined to the visitor’s real session
Search engine crawlers always see your original number so indexed listings stay consistent, and account admins are emailed when a pool runs at capacity. See Phone Tracking

Listings & local presence

New Marketing > Listings page — one health-and-action card per Google Business Profile location: a 0–100 Listing Score with a full breakdown, live profile data (hours, categories, attributes, contact info), warnings straight from Google (unverified, duplicate, marked closed), and a daily score history so a fix visibly moves the needle
Every failing check comes with the action that fixes it: inline edits validated with Google before they apply, Fix with AI proposals applied only after you approve, and tracked tasks for name and address edits — those trigger Google re-verification, so they are deliberately not one-click
Attributes audit — every attribute Google offers for your location’s category versus the ones you’ve set, with the top gaps named. Often the cheapest local-visibility win available
Directory coverage with honest provenance: every claim is labeled synced, detected via scan, confirmed, or self-reported — never a fake sync. Includes an on-demand Google Maps presence scan (claimed status, public-data drift, possible duplicates; re-runs monthly on its own) and a guided checklist for Apple Business Connect, Bing, Yelp, and Facebook with per-field NAP copy helpers
No more false alarms: a connected-but-unconfigured profile says “finish setup” instead of erroring, a client marked as having no Business Profile is skipped in reports, health checks, and AI analysis, and a failed sync always shows the last saved data with its date
Listing health now flows into client reports (new listings section) and the weekly SEO digest, which calls out low scores, unverified locations, and Google-flagged duplicates. See Listings

Advertising: attribution columns & audience sync

The PPC Dashboard’s campaign table now shows what happened on your side after the click: Identified visitors, ICP Match, Calls attributed via call tracking, Contacts, Deals (with won count), and Sales — click a count to see exactly who is behind it
Audiences built under Marketing > Audiences can now sync to Google, Meta, TikTok, LinkedIn, and Vibe as customer-match / custom audiences over your existing ad connections — adds and removals stay in sync, the platform’s matched count reports back, and identifying data is hashed before upload so raw emails and phone numbers never leave Hiveku
When a platform gates an upload (Meta’s Custom Audience terms, Google’s Customer Match eligibility), the sync row shows the reason and what to do about it. See Advertising Campaigns

Client portal expansion

Portal lists (invoices, payments, estimates, contracts) are now full data tables — search, status filter, sortable columns, pagination — with an Export CSV button that downloads exactly what the current search and filter show. Invoices and estimates also get Download PDF
New Payments tab in the portal — a searchable, exportable history of every payment a client has made. Turn it on with the See their payment history toggle under Commerce → Settings → Client portal
Helpdesk live chat inside the portal — the launcher opens already signed in as the client (no name-and-email form), and each conversation opens a ticket linked to their contact record. Toggle: Show the live-chat widget; requires the helpdesk to be enabled on your account
Manage client contacts without leaving portal settings — add, edit, bulk-send sign-in links, and remove contacts from the Client contacts card. Changing a contact’s email signs them out of all active portal sessions
Invite to portal — a customizable welcome email (edit the subject and body under portal settings → Emails), sent from your own verified domain, optionally granting company-wide billing access in the same click
Open as — view the portal exactly as a client sees it, read-only: payments and changes are blocked, an amber “Viewing as” banner stays on screen, and the session expires after 60 minutes. See Client Portal

Payment pages

New Commerce → Payment pages: a hosted checkout at a public link that takes a payment from anyone — no invoice to send first. Every payment still creates a paid invoice and a receipt, so it lands in your reports like any other
Links are served from your own host — your verified custom domain when you have one — and default to an unguessable name you can shorten to something printable whenever you want to put it on paper
Control what a payer can enter (quick-pick amounts, fixed-amounts-only, or a min/max range) and what the form asks for — name, company, phone, a reference field, type-the-email-twice — with reorderable field order and tax-exemption claims
A customizable payer confirmation email with merge tags and a Send a test to me button, sent from your verified sending address when your commerce email domain is set up
CRM automations on payment: every payer becomes a contact without overwriting data you have curated, and you can optionally create and link their company and open a deal in a pipeline and stage you choose
A webhook on every successful payment with a write-only bearer secret and a Send a test event button, plus per-page views, payments, conversion, and collected totals. Double-charge protection and card-testing rate limits are built in. See Payment Pages

Call recap emails

Every completed call now sends a recap email — and it knows who handled the call. A call your AI agent handled arrives as an AI call recap; a call a teammate placed or answered arrives as a Call recap naming that person
Recaps now reach the teammate who actually took the call, not just the account’s owners and admins
When the call was recorded, the recap includes a Listen to the recording button that opens the call in your dashboard with the recording ready to play. Recordings are never attached to the email and never exposed through public links
Calls land on the matching CRM contact’s activity timeline, attributed to the teammate (or AI agent) who handled them
Configure the email, in-app notification, transcript inclusion, and recipients under AI Agent > Call recaps & notifications — and use Simulate call to send yourself a test recap. See the Communications Overview and AI Voice Agent

Rich MMS everywhere

The SMS composer gained an emoji picker, GIF search, and image attachments (up to 10 per message) — in the SMS inbox, on CRM contact pages, in replies to SMS helpdesk tickets, and in sequence SMS steps
Scheduled sends and sequence steps now deliver their attached media. Previously they silently sent the text and dropped the media. Media-only messages with no text are also now valid
Size limits are type-aware with a clear error instead of a silent failure: still images up to 5 MB (carriers resize these in transit), animated GIFs, video and audio capped at 600 KB, because carriers strip oversized media while still delivering the text — the reason a GIF could show as delivered yet arrive blank. The GIF picker now picks a rendition small enough to deliver on its own
Inbound texts appear in the open inbox in real time — no refresh needed
The Sales and Helpdesk AI agents can now text in the conversations they work. The recipient is locked to the contact or ticket — an agent can never text an arbitrary number — and every agent send passes the same opt-out, registration and sending-cap gates as a manual send. See SMS Messaging

SMS opt-out handling

A text starting with STOP, UNSUBSCRIBE, CANCEL, END, QUIT or STOPALL opts the sender out automatically, and every send path — manual, bulk, scheduled, automation, and AI agent — refuses opted-out recipients from that moment. START or UNSTOP opts back in, and confirmations are sent automatically. Nothing to implement
New Do not text list on the Compliance tab showing every opted-out number. Add a number by hand when someone asks you to stop by phone or email — the obligation is the same, and the list is your record of honoring it. Removal is only appropriate with documented consent to resume texting
A bare STOP no longer rings your whole team’s notifications — it is fully auto-handled, and the message still lands in the thread and audit trail. “STOP texting me” is a human talking and still notifies
A newly purchased number can receive STOP texts meant for its previous owner — numbers are recycled, and strangers may still have old threads with them. These opt-outs are honored automatically and are nothing to worry about. See Compliance and Recording

Multiple mobile devices per person

Sign in to the mobile app on as many phones as you like — each phone now registers as its own device, and all of them ring on incoming calls
New Mobile devices panel on the Extensions tab listing every phone signed in to the app: owner, device model, OS and app version, the extension it rings, when it was last seen, and its push notification health
Stop ringing this device revokes a lost phone or a former employee’s device instantly — incoming calls stop reaching it, and it only rings again if someone signs back in to the app on it. See Extensions and Devices

Reports Hub & Client Reports (beta)

The reports page at Marketing > ROI Reports is now a full Reports hub with four tabs — Overview (campaign ROI attribution), Client reports, Journeys, and Custom (AI-built sheets and report sections) — each with its own shareable URL
New client reports: scheduled cross-channel reports covering paid ads, SEO, local listings, social, email, calls, and website traffic — branded with your account name and logo, every number paired with a prior-period comparison, shared as a single public link that needs no login
Weekly, monthly, or manual-only schedules; saved recipients receive every scheduled run by email, and a Send now button handles one-offs. Reports are snapshots — they update on schedule or on Regenerate, never silently in between
Channels you haven’t connected simply don’t appear in a client report, and one channel’s data failing never blanks the rest — the report renders with a short note listing what’s missing
The campaign ROI Overview gained custom date ranges, asset-type filter chips (Email, PPC, Social, Content, Sequence, Cold email), a Solid-matches-only toggle, CSV export, and an amber warning when ad spend data is more than 3 days stale
Rolling out in beta — see the Reports Hub docs

AI chat: send follow-ups while the AI works

Prompts sent while the AI is busy now queue and run in order, one at a time, instead of being dropped or forcing you to wait for the turn to finish
A queue strip above the message input shows what is waiting. Expand it to reorder prompts by dragging, inspect their text and attachments, remove one, or clear all with confirmation
Interrupt & run next stops the current turn and starts the next queued prompt immediately. Stopping a turn pauses the queue until you click Resume
A queued prompt that fails to start is tried again automatically, then parked visibly with a Retry button after 3 attempts. Queued prompts are never silently deleted
Stopping a turn mid-edit now discards that turn’s unsaved changes cleanly, so a cancelled prompt never leaves half-applied edits in your project
The queue runs on the server, so queued prompts keep running in order even if you close the tab. See Message Queue

Undo this turn, rebuilt

Undo this turn now reliably reverts everything an AI turn changed. Restore points reflect your project as of the moment you sent the prompt, so an undo can no longer include the turn’s own edits
Turns that added pages or files are now fully undoable: files the turn created are removed, not just modified files restored
A new confirmation dialog lists exactly which files will be restored or removed, then shows live progress with named phases and elapsed time. You can send it to the background, and closing it never cancels the restore
Before anything changes, your current state is pinned as a safety checkpoint, so every undo is itself reversible from checkpoint history
The outcome summary now tells you what was restored, what already matched, and which files were removed, and a failed preview refresh is reported instead of showing success
Fixed the preview reload storm after an undo, and replaced the browser confirmation popup that Chrome could silently suppress, which made the button appear dead. See Undo an AI Turn

37 new workflow nodes across five new categories

Five new node categories join the editor: Creative Studio, Web Research, Voice, Accounting & Billing, and Health & Safety Checks — the Add Node picker now spans 350+ nodes in ~30 categories
Creative Studio generates AI images (single or sets of up to 10), short AI video clips, and royalty-free stock photo searches inside a workflow, feeding straight into CMS or social steps
Web Research brings live search, single-page scrape, site crawl (up to 50 pages), LLM extraction with a JSON schema, and fast sitemap-based URL mapping
The CMS family can now read as well as write: Read Entry, Search Entries, List Collections, Delete Entry (draft-aware), and Bulk Import of up to 200 entries in one call — so workflows can dedupe-check before writing
Accounting action nodes pair with the billing triggers — record bill and invoice payments (with idempotency keys so a replayed run can’t book twice), AR/AP aging, and P&L summaries — while Voice nodes give read-only access to calls, transcripts, AI summaries, and numbers
Health & Safety Checks make self-monitoring automations possible: test an integration’s auth, diagnose a broken deploy or missing conversion tracking, snapshot a checkpoint before risky steps, and audit account drift. See the new Workflow Node Reference

Merge variables never leak into customer messages

An unresolved {{variable}} in any workflow node is now dropped instead of being sent as literal curly-brace text — no more {{trigger.phone}} showing up in a CRM record or an outbound email
A field whose entire value fails to resolve is omitted: a create leaves it unset, and an update leaves the existing value alone instead of clearing it
Every miss is flagged on the affected step in the run inspector (“N merge variables resolved to nothing”), so a typo’d tag surfaces in Run History rather than in someone’s inbox
Where an empty fallback would be dangerous, the node now refuses to run instead — for example, a phone call node errors rather than dialing with the default caller ID

SMS triggers: scoping, full message text, and MMS

The SMS Received trigger’s “To this number” filter is now enforced — a workflow scoped to one of your numbers fires only for texts sent to that number, instead of every number on the account
The trigger payload now carries the full message text (previously truncated to a short preview), the sender’s matched CRM contact, and MMS attachments via {{trigger.media}}
If a scoped trigger can’t determine the receiving number, it stays quiet rather than firing for the wrong number

CMS: real publishing, scheduling, and a rebuilt editor

Every entry now shows one derived status — Draft, Published, Scheduled, or Archived — computed from the same rules your site uses to decide what renders, so the badge never disagrees with the live site. The entry sidebar shows exactly the actions valid for that state: Publish, Schedule, Unpublish, Archive, Publish draft, Restore
Scheduled publishing that actually publishes: pick a date and time, and the entry goes live then — with an automatic production deploy by default (staging, dev preview, or no-deploy are one click away). Several entries scheduled together share a single deploy, and failed attempts surface their error instead of vanishing. See Scheduled Publishing
Edits autosave into a private draft as you type — nothing reaches the live entry until you Save or Publish, and a published entry with pending draft edits says so with an amber dot plus Publish draft / Discard draft actions
Publishing is honest about deploys: the sidebar’s Deploy state section shows Production, Staging and Dev, and an amber “Published changes aren’t live yet” card offers a one-click Deploy. Manual publishing never deploys behind your back
The panel itself was rebuilt: a collections rail with groups and live entry counts, a real entries table (status filter chips, a column picker with drag-to-reorder, 25/50/100 page sizes, a tree view for hierarchical collections), and bulk Publish / Unpublish / Archive / Set field / Delete with per-row results — one bad row never sinks the batch
New collections start from one-click presets — Blog, Products, Team Members, Testimonials, FAQs, Case Studies, with reference targets and publish fields included — or from a visual schema builder with per-field settings, drag-to-reorder, and nesting up to four levels. See the updated CMS docs

Section Library

Browse 1,700+ professionally designed page sections — heroes, feature grids, pricing tables, testimonials, headers, footers — in the website editor’s new Components pane, every one with a preview thumbnail
Click a section in your live preview and the catalog narrows to designs in that section’s category — click a hero, see heroes
Use in chat writes a precise swap instruction into the AI chat that preserves your existing copy; Replace section now swaps the design in place instantly while you’re still blocking out a page
Sections arrive as normal, editable code in your project — restyle them, rewrite them, or hand them back to the AI like anything else you built. See Section Library

Every Hiveku site now ships a branded 1200 x 630 share card by default, so links shared on Facebook, LinkedIn, X, and Slack get a proper preview instead of a cropped logo or a gray box
The default is deliberately shy: it only appears when your project has no custom card, and a page-specific or site-wide image you set always wins
Pages that customize other social fields (a share title, a description) no longer lose the image — the site default fills in wherever a page doesn’t bring its own
Static sites get share-image, canonical, and Twitter-card tags by default too
Changed your card but the old preview keeps showing? That’s the platform’s scrape cache — Social Share Cards covers how to force a refresh

Design Studio: AI video generation

Brief in, MP4 out: describe the video you want and the AI plans a storyboard of scenes — AI clips, stills, and canvas layouts — then generates, voices, scores, and stitches it
Nothing renders and nothing is charged until you approve: the storyboard card itemizes every scene and puts the exact price on the button — Approve & generate — $4.80. Approval is always a human action
A Video tab inside the design editor holds the whole flow — approval, live per-scene progress, and the finished video — no separate page, no refreshing
Revise one scene without regenerating the video: hover its tile, describe the change, confirm the cost. The new scene is seeded from the current frame so it stays continuous
Your logo and all text are composited as crisp overlay layers, never baked into AI footage — no melted lettering
Narrator voices are brand assets: audition and approve voices under Branding → Voiceovers, set a default narrator, and videos can only speak in voices your account approved. See AI Video

Add an optional First comment to any post — it publishes automatically as the post’s first comment the moment the post goes live, with nobody online. Facebook and LinkedIn show posts containing outbound links to fewer people, so moving the link into the first comment usually reaches more of your audience
Works on Facebook, Instagram, LinkedIn (personal profiles and company Pages) and X. Instagram also gets its own per-platform first-comment field, the classic home for a hashtag block that would otherwise clutter the caption
Paste a URL anywhere in the post body and the composer now detects it and shows an editable link preview card — adjust the title, description and image before publishing. Closing the card removes the link from the post entirely, so a hidden URL can no longer publish silently
Facebook and LinkedIn render their own link cards from the URL, so the card you preview is the card your audience sees
Account chips in the composer now carry a platform badge on each avatar, so the same brand’s Facebook Page and Instagram profile are distinguishable at a glance
See the Composer

A post scheduled for later no longer risks going out early: once a date is set, Save & Schedule becomes the primary button, and Publish Now asks for confirmation — naming the scheduled time — before discarding the schedule
The posts list gains a Stats column: impressions, likes, comments and shares for every published post, summed across the platforms it went to. The first sync runs about 30 minutes after publishing
Google Business Profile posts show a dash rather than waiting forever — Google discontinued per-post statistics
Facebook impressions require a permission that Pages connected before August 2026 didn’t grant. Reconnect the Page under Marketing > Social > Accounts (one click, history preserved) to enable them; likes, comments and shares flow either way
Reply to Facebook and Instagram comments straight from the Engagement inbox — previously LinkedIn only. Replies thread under the comment on the platform exactly as if you’d replied natively, and your own replies don’t echo back into the inbox
See Analytics and the Engagement inbox

New Timezone setting under Settings > General. Set it and every scheduled-post time you pick means that zone — an operator in Chicago scheduling “3:00 PM” for a Sydney client gets Sydney’s 3:00 PM
The composer names the zone right under the picker and shows the equivalent in your own time, so there’s never a question of whose clock you’re on. The calendar, queue and suggested best-time chips all render in the same zone
Leave it unset and nothing changes — times mean each viewer’s own timezone, exactly as before
Daylight saving is handled correctly: a post set for 9:00 AM stays 9:00 AM on the wall clock, even when a DST transition falls between scheduling and publishing
See the Composer

Outbound pipeline stage automation

Cold-email board columns are now configurable rules — define what puts a lead in each stage (reply category, lead tags, the Interested flag, or reply classification), optionally scoped to specific campaigns
Entering a stage can create CRM records automatically: a contact (created or updated, never duplicated), the company, and a deal with a configurable pipeline, stage, value, currency, name template, and owner
Each automation runs once per lead per stage — a lead re-entering a column never creates a duplicate deal, and the deal is never modified or deleted afterward
A live “N leads match” preview shows a rule’s reach as you edit, and switching automation on above 200 matching leads asks for confirmation with the exact count before anything is created
Dragging a card by hand pins it so rules won’t move it back, and asks before running the target stage’s CRM automation — pausing the sequence is now an explicit per-stage choice instead of a silent side effect of every drag
Board columns now show exact lead counts with per-column paging, plus an always-present Unassigned column so leads matching no rule stay visible — see Outbound Lead Pipeline

Form capture: spam protection and duplicate prevention

Every captured form submission is now scored for bot fingerprints the moment it arrives — filled honeypots, inhuman submission speed, burst rates, link-only bodies, disposable email domains. Suspicious submissions are filed under the Spam filter in Analytics → Forms and never emailed to you, never added to your CRM, and never fire a workflow
Nothing is ever deleted. A spam-filed submission stays visible and is one click from restored — Not spam returns it to your inbox and delivers the notification email it was originally denied, within a few minutes
Optional Google reCAPTCHA on every form: toggle Form spam protection on under Hosting → Integrations, per environment. It is invisible — no checkbox, no puzzle, and Google is not contacted until a visitor focuses a form field. No keys or Google account needed; it runs on Hiveku’s platform configuration
Pick how aggressive to be, per project: Lenient files only certain spam, Balanced is the default, Strict files borderline submissions too — because a false positive on a high-value quote form costs more than one junk email does
One form under sustained attack can require a visible “I am not a robot” checkbox on just that form, from the Forms tab’s per-form settings, leaving the rest of your forms friction-free
One physical submission is now exactly one lead. Captures of the same submit seen through different channels are linked into a single row, a single notification email, and a single CRM contact — and URL variants like a trailing slash no longer split one form into duplicate records in the Forms tab. See Form Submissions

Sensitive (write-only) environment variables

Mark any environment variable Sensitive to make it write-only. After you save, the value is hidden everywhere in Hiveku and cannot be revealed again — not by teammates, Hiveku staff, AI agents, or the VS Code extension. Builds and deployments still receive the real value
Leave the blank field alone on later saves to keep the stored value — blank never means clear for a sensitive variable, so renaming it, changing its environments, or editing other rows never requires re-entering anything
To change a sensitive value, click Replace value and supply a new one; a sensitive variable can never be saved empty. To make it readable again, untick Sensitive while supplying a replacement at the same time
Branch and pull-request previews now receive development values, never production ones. If a variable is scoped only to Production, add a Development or All Environments value so previews still work
See Environment Variables

Mobile app on multiple phones

Sign in to the Hiveku app on as many phones as you like — each phone now registers as its own device with its own extension, and incoming calls ring all of them
Every phone identifies itself, so you can tell devices apart: model, OS and app version, the extension it rings, when it was last seen, and its push notification health
New Mobile devices panel on Communications → Extensions lists every phone signed in to the mobile app across your team
Stop ringing this device silences a single phone — the lever for a lost phone or a former employee’s device. It only starts ringing again if someone signs in to the app on it
Needs app version 1.2.8 or later. Phones on older builds keep working on a shared extension and show an “older app build” badge until they update
See Hiveku Mobile App and Extensions and Devices

Mobile app experience overhaul

The app feels faster everywhere: buttons respond when pressed, screens show skeleton previews while loading, lists keep their results on screen while you filter, and detail screens open instantly from data the app already has
Platform-native polish: haptic feedback, cached images, long-press to copy, system share sheets, and home-screen shortcuts — press and hold the app icon for Dial, New chat or Inbox
Links to app.hiveku.com now open directly in the app, already signed in — no browser detour, no second login
Android notifications get one channel per category, so silencing one type no longer silences the rest, and the app icon shows an unread badge on both platforms
New global Search across contacts, companies, deals, projects and tickets, plus a customizable tab bar — drag to reorder, Chat and More stay pinned at the ends
iPad layouts, VoiceOver and TalkBack labels across the app, and most updates now install themselves in the background when you open the app — no store update needed. See Hiveku Mobile App

July 2026

Call tracking and dynamic number insertion

Attach a tracking number pool to a website project and every visitor sees their own number — swapped into tel: links and any configured plain-text numbers, rendered in the same visual format as the number it replaces, extensions preserved
Assignments are sticky: a visitor keeps their number for about 30 minutes of browsing, extended after they call, so page navigation and quick return visits show the same number
Every tracked call ties back to the visitor’s session — UTM source, medium and campaign, landing page, referrer, and ad click IDs from Google, Facebook, Microsoft and TikTok
New Calls view on each project’s Analytics tab: answered/missed/duration KPIs, per-campaign call counts, and a call log with inline recording playback
Missed-call SMS autoresponder texts the caller the moment an inbound call is missed or goes to voicemail, with merge variables and a live segment counter
Opt-in Google Ads offline conversion uploads push attributed calls back to Google Ads so Smart Bidding learns which campaigns make the phone ring — with answered-only and minimum-duration policies and an optional conversion value. See Phone Tracking

Workflow automation overhaul

The Form Submitted trigger now fires for every form submission path — embedded forms, hosted forms, and forms captured on deployed sites all reach your workflows, with spam and duplicate submissions filtered out before the trigger fires
AI Agent nodes can route to a department agent (with your brand voice, memory, and tools) instead of a bare model, return structured JSON you can branch on with a Condition node, and run specialist sub-agents whose findings feed the main prompt
New Test Run button in the editor — watch each node light up on the canvas with its output as it executes; nodes that would send, publish, or charge are simulated and show exactly what they would have done. Enabling a workflow now validates it first and names any broken node
Merge variables got a real editor: type {{ in any text field for autocomplete, and inserted references render as pills that show whether they resolve. Unresolved variables are listed per step in the run inspector
Fairer auto-pause: manual runs, Test Runs, and replays never count toward the failure circuit breaker, so iterating on a half-built node can’t pause a workflow whose live traffic is healthy. Auto-pause now emails account owners with the reason and a resume link, and resuming replays every trigger event that arrived while paused, oldest first
New daily AI budget: each workflow may execute at most 200 AI-agent node runs per day (25 per run). Crossing it pauses the workflow and emails the owners, so a mis-wired loop can’t burn AI credit overnight

May 2026

GitHub source-of-truth model

When GitHub is connected to a project, GitHub is now the canonical source of code — the Hiveku database is a working buffer reconciled against GitHub at every deploy
AI chat sessions auto-commit to GitHub at session end. A 10-second debounce batches back-to-back chat turns into a single hiveku[bot] commit, prefixed [hiveku] Sync from Hiveku
Bot commits never trigger an auto-deploy. The auto-deploy toggles continue to fire only for pushes made outside Hiveku (your laptop, VSCode, external collaborators, GitHub Actions, etc.)
Every deploy starts with a pre-deploy sync. If the database and GitHub have BOTH modified the same file since the last sync, the deploy is paused with a conflict notice — you pick which version wins, then retry. Previously these conflicts could silently overwrite work
External MCP agents (Claude Code, Cursor, etc.) gain a project_commit invariant — tool descriptions now state that committing is required for persistence on GitHub-connected projects, with explicit warnings about the auto-overwrite risk
See GitHub Integration for the full model and Deployments for how the pre-deploy sync gate works

Native Mobile (Expo) project type

New project type — pick Native Mobile in the new-project dialog to scaffold a real Expo Router app with Supabase auth, items CRUD, NativeWind, and protected route groups; Supabase database is provisioned automatically
Per-project Fly.io preview running Metro + React Native Web inside an iPhone/Android phone-frame chrome (11 device presets, landscape mode, accent color picker — selection persists per-project in localStorage)
AI agent trained on Expo Router + NativeWind conventions; knows the difference between an OTA-deliverable JS edit and a native-dependency change that requires a Build & Ship
Mobile Credentials page — connect your Apple Developer (.p8 ASC API key) and Google Play (service account JSON) accounts; live preflight validation via signed JWTs, encrypted storage in AWS Secrets Manager
One-click Build & Ship — kicks off parallel iOS + Android EAS builds, auto-creates the iOS App Store Connect record on first build, and auto-submits to TestFlight + Play Console Internal track
Build cancel button, email notifications on success/failure, decoded Apple/Google error messages with Fix with AI deeplink (~60% of common failures resolvable end-to-end)
OTA Update channels (Preview + Production) with atomic Promote button; bundle size warnings (amber at 75 MB, red at 100 MB) with per-package breakdown
App Store Assets generator — one form turns app name + tagline + accent color into a 1024×1024 icon, splash screen, and store-listing copy (subtitle, description, keywords)
GitHub integration parity with web projects — Build & Ship tags the commit, AI edits auto-commit, .env excluded from sync
See the Mobile Quickstart to ship your first build in ~60 minutes

Design Studio — Layered Motion Graphics

New animated design surface at /dashboard/marketing/design/ — every text, shape, image, and CTA stays an editable Fabric layer while motion plays
Animation is a property of layers (not a baked MP4), so dragging the headline mid-playback, retyping any word, or swapping a color via the picker keeps motion working
AI design agent generates the static frame using your brand kit, then animates each layer with coherent strategies — Cascade Fade-Up, Kinetic, Hero Scale + Fade, or Slideshow
14 enter/exit presets + 4 loop motions (pulse, wiggle, breathe, rotate-slow) shared across the AI tool, the per-layer Style panel editor, and the MP4 export compositor
18 layered animated starter templates spanning Instagram / Reel / TikTok / YouTube / email-banner surfaces — fully editable from frame zero, no template lock-in
Per-layer animation editor in the right Style panel with debounced sliders (250ms), auto-pause on selection, and snapshot-and-restore runtime that prevents drift
Canvas-level Animation panel with one-click strategy buttons that preserve existing loop motions when re-strategizing
MP4 export via Remotion render worker; PNG export client-side for static designs
See the Design Studio docs for full coverage

April 2026

Hiveku CMS (Webflow-style structured content)

New manifest-driven CMS — declare collections in hiveku.cms.json with typed fields, references, and validation
CMS panel in /v3 with a Webflow-style entry list, form editor, version history, and bulk import
File-backed storage: MDX for blog-like content, JSON for structured data — all in content/
AI-driven scaffolding: agents read your existing site and migrate hardcoded data into the CMS
13 supported field types including reference for linking collections (blog → author, product → category)

Email Marketing Agent

New Email Marketing department with a full ESP (audiences, campaigns, templates, sequences, deliverability)
AI coach “Lumen” embedded on every email page — drafts newsletters, builds audiences, triages deliverability
Default memory, 4 skills, 3 rules, and the coach persona auto-seeded on first enable
Cross-agent delegation: content, branding, and ppc agents can hand work to the email team

Sales AI Co-pilot

AI co-pilot layered on top of CRM — drafts replies, summarizes meetings, surfaces follow-ups
Approval-first: every draft and suggestion stages in a pending actions queue
Reads meeting transcripts, calendar, and contact activity for full context
New how-tos for AI SDR, sales sequences, and reminders

Calendar & Booking

Calendly-style scheduling built into Hiveku
Meeting types, availability rules, public booking page, embeddable widget
Bookings flow into CRM and trigger workflows automatically
Team calendars with multi-member availability sync

Communications (Voice & SMS)

Production phone system with inbound/outbound calls, IVR, voicemail, call recording
Phone number provisioning, extensions, ring groups, call queues
AI agent routing — calls can be handled by an AI agent with handoff to human
SMS sending via Twilio integration
E911 compliance built in

Commerce

Invoices, estimates, contracts (with e-signature), subscriptions, payments
Client portal for customers to view and pay invoices
AR aging, MRR/ARR reports, payment trend dashboards
Product catalog and order management coming soon

Better Stack Integration

Added uptime monitoring for app.hiveku.com
Incident alerting via phone and email

Documentation Launch

Launched public documentation on Mintlify
API reference for Builder, Marketing, CRM, and Workflows
100+ how-to guides covering every major feature

Recent Highlights

AI Builder Enhancements

Multi-model support via OpenRouter (GPT-5.4, Claude, Gemini, Grok)
AI mode switching (Coder, Designer, Full-Stack)
Context condensation for long conversations
Model failover with automatic retry

Visual Editor

Click-to-edit WYSIWYG editing
Component library with drag-and-drop sections
Figma import with multi-page support

Marketing Suite

Social media scheduling with LinkedIn integration
Outbound email with lead management and sequences
Content management with review workflows
SEO tools with Google Search Console integration

Multi-Runtime Deployment

Support for Next.js, Python, Go, PHP, Ruby, .NET, Rust
AWS ECS containers with automatic SSL
CloudFront CDN
Custom domain support

Database Management

Supabase PostgreSQL provisioning
SQL editor with direct query execution
Automated backups to S3
Point-in-time restore via checkpoints

Workflow Automation

Visual workflow builder
Webhook, schedule, and database triggers
Dead letter queue for failed executions
Version history and rollback

​October 2026

​Email: the content of a sent email is kept 30 days

​Publishing: a broken publish goes back to the version before it

​Editor: checks and a preview for open reviews, and type check, lint and tests before merging

​Dashboards: Workspaces you can customize, role pages and more ticket buttons

​Fixes: recurring bills, ad connections, call notes and the Monday paid ads email

​Paid ads: working Amazon Ads and Vibe connections no longer say “Token expired”

​Branches and publishing: one approval rule for everyone, and plainer words

​Dashboards: your home is a dashboard you can arrange

​Dashboards: your own data, buttons and forms

​Team activity, with a weekly leaderboard

​Workspaces and AI apps

​Branches: reviews, comments, the merge line, and three rules for how changes reach Your site

​Payment pages: three types, and subscriptions people sign up for themselves

​Subscriptions and invoice payments: restarting Unpaid, and 3-D Secure on invoices

​Subscriptions: a staff free trial renews on the day it ends

​Saved cards: the cardholder’s name goes with every card on Authorize.Net

​Project management: statuses that mean what your team means

​Project management: creating and running projects

​Project management: who may change what

​Project management: deleting keeps the record

​Sites

​Moving a project or site to another workspace

​Claude Code

​September 2026

​Versions: every change saved, and a way back

​Hosting: the Firewall section keeps your site’s own refusals apart

​Forms: choose which forms Hiveku captures

​AI agents: report a problem with Hiveku, or ask for a missing tool

​Hosting: the Firewall section, and the evidence behind every row

​Content: a named author, the SERP brief, a thesis and five titles, site architecture, bottom-funnel pages, the decision loop, and conversion inside the piece

​Content: distribution on every piece, leads per piece, proof you can cite, and research that stays

​Images: GPT Image 2.5 by default, the brand image profile, and article images in one step

​Content: grounded drafts, a pre-publish check, real internal links, and a calendar that shows what will publish

​Webflow: the content-source switch, and every write pair asks on both halves

​Webflow: keep the site in Webflow, run it from Hiveku

​Creative Studio: brand-aware images, a media toolkit, and fonts that survive export

​File uploads on website forms

​Working branches in the editor

​August 2026

​Accounts can no longer be deleted out from under the people who live in them

​PPC depth tools on every platform

​SEO delivery: live rank tracking, page intelligence, and the Tag Manager pipeline

​Client reports and the two-key approval rail

​Standing marketing playbooks

​Call tracking: keyword-level attribution and every-platform conversion send-back

​Client portal and payment pages overhaul

​Domains: buy, transfer and manage

​Sensitive (write-only) environment variables

​Environment Variables editor rebuilt

​Security fixes

​August 2026

​Number porting

​Call tracking: repeat callers, faster recycling, and the swap tester

​Listings & local presence

​Advertising: attribution columns & audience sync

​Client portal expansion

​Payment pages

​Call recap emails

​Rich MMS everywhere

​SMS opt-out handling

​Multiple mobile devices per person

​Reports Hub & Client Reports (beta)

​AI chat: send follow-ups while the AI works

​Undo this turn, rebuilt

​37 new workflow nodes across five new categories

​Merge variables never leak into customer messages

​SMS triggers: scoping, full message text, and MMS

​CMS: real publishing, scheduling, and a rebuilt editor

​Section Library

​Social share cards on every site

​Design Studio: AI video generation

​Social composer: first comments and link previews

​Social: safer scheduling, post stats, and comment replies

​Social: schedule in your client’s timezone

​Outbound pipeline stage automation

​Form capture: spam protection and duplicate prevention

​Sensitive (write-only) environment variables

​Mobile app on multiple phones

​Mobile app experience overhaul

October 2026

Email: the content of a sent email is kept 30 days

Publishing: a broken publish goes back to the version before it

Editor: checks and a preview for open reviews, and type check, lint and tests before merging

Dashboards: Workspaces you can customize, role pages and more ticket buttons

Fixes: recurring bills, ad connections, call notes and the Monday paid ads email

Paid ads: working Amazon Ads and Vibe connections no longer say “Token expired”

Branches and publishing: one approval rule for everyone, and plainer words

Dashboards: your home is a dashboard you can arrange

Dashboards: your own data, buttons and forms

Team activity, with a weekly leaderboard

Workspaces and AI apps

Branches: reviews, comments, the merge line, and three rules for how changes reach Your site

Payment pages: three types, and subscriptions people sign up for themselves

Subscriptions and invoice payments: restarting Unpaid, and 3-D Secure on invoices

Subscriptions: a staff free trial renews on the day it ends

Saved cards: the cardholder’s name goes with every card on Authorize.Net

Project management: statuses that mean what your team means

Project management: creating and running projects

Project management: who may change what

Project management: deleting keeps the record

Sites

Moving a project or site to another workspace

Claude Code

September 2026

Versions: every change saved, and a way back

Hosting: the Firewall section keeps your site’s own refusals apart

Forms: choose which forms Hiveku captures

AI agents: report a problem with Hiveku, or ask for a missing tool

Hosting: the Firewall section, and the evidence behind every row

Content: a named author, the SERP brief, a thesis and five titles, site architecture, bottom-funnel pages, the decision loop, and conversion inside the piece

Content: distribution on every piece, leads per piece, proof you can cite, and research that stays

Images: GPT Image 2.5 by default, the brand image profile, and article images in one step

Content: grounded drafts, a pre-publish check, real internal links, and a calendar that shows what will publish

Webflow: the content-source switch, and every write pair asks on both halves

Webflow: keep the site in Webflow, run it from Hiveku

Creative Studio: brand-aware images, a media toolkit, and fonts that survive export

File uploads on website forms

Working branches in the editor

August 2026

Accounts can no longer be deleted out from under the people who live in them

PPC depth tools on every platform

SEO delivery: live rank tracking, page intelligence, and the Tag Manager pipeline

Client reports and the two-key approval rail

Standing marketing playbooks

Call tracking: keyword-level attribution and every-platform conversion send-back

Client portal and payment pages overhaul

Domains: buy, transfer and manage

Sensitive (write-only) environment variables

Environment Variables editor rebuilt

Security fixes

August 2026

Number porting

Call tracking: repeat callers, faster recycling, and the swap tester

Listings & local presence

Advertising: attribution columns & audience sync

Client portal expansion

Payment pages

Call recap emails

Rich MMS everywhere

SMS opt-out handling

Multiple mobile devices per person

Reports Hub & Client Reports (beta)

AI chat: send follow-ups while the AI works

Undo this turn, rebuilt

37 new workflow nodes across five new categories

Merge variables never leak into customer messages

SMS triggers: scoping, full message text, and MMS

CMS: real publishing, scheduling, and a rebuilt editor

Section Library

Social share cards on every site

Design Studio: AI video generation

Social composer: first comments and link previews

Social: safer scheduling, post stats, and comment replies

Social: schedule in your client’s timezone

Outbound pipeline stage automation

Form capture: spam protection and duplicate prevention

Sensitive (write-only) environment variables

Mobile app on multiple phones

Mobile app experience overhaul