Billing
Hal is billed per identity, with an invoice generated on the first of each month for that month and charged to a card or US bank account saved with Stripe. The rate, the minimum and what is counted are on the pricing page. This page is what billing looks like from your portal and your inbox. Hal’s AI usage is a separate bill, from Anthropic to your own account: Controlling AI spend.
Settings → Billing
Settings → Billing is where an administrator sees and manages billing:
- The payment method. Green with the card or bank account on file; red with what needs doing, when none is on file or the last charge failed, in Stripe’s own words.
- The status line. When your evaluation ends and billing begins, at what rate, and what the first invoice covers; once you are paying, the rate and how you are invoiced; after notice to end the service, the date it ends.
- Manage payment method and invoices, which opens Stripe’s billing page: replace the card or bank account there and see your invoices. Card and bank details are entered with Stripe and never pass through HAL AI’s systems.
- The counts, taken once a day. Billable Count is the day’s figure, the greater of its identities and its endpoints; Monthly High-Water is this month’s highest so far, and Previous Month’s Peak last month’s. Endpoints is what your servers, workstations and network devices count as, with how many of each. A table gives each client’s identities, tenant by tenant, and its servers, workstations and network devices, and a chart tracks the daily billable count with its identities and endpoints.
How each invoice is worked out
The invoice is generated on the first of each month for that month, at the previous month’s peak: the highest daily billable count recorded in the month before, which is already on Settings → Billing, as Previous Month’s Peak, when the invoice arrives. The first invoice after an evaluation that began in the same month uses the evaluation’s peak instead, which is on Monthly High-Water. The invoice is charged to your payment method when it is issued, and Stripe emails the invoice and its receipt to your billing contact.
When the evaluation ends
Nothing is charged during the 14-day evaluation. Through its final week Hal reminds you when billing begins: an EVALUATION line in the daily digest, a banner on the dashboard and the Health page, the status line on Settings → Billing, and an email to the owner on your account, with your billing contact copied. Each gives the day billing begins and the rate. The status line, the digest line and the email also give what the first invoice covers; the digest line and the email give the peak billable count it is based on, and today’s billable count.
The first invoice is issued and charged the day after the evaluation ends, for the rest of that month, prorated by day. If no valid payment method is on file then, Hal pauses until that invoice is paid. To end the evaluation instead, an administrator asks Hal to cancel, in the portal’s chat, on or before its last day: Hal stops at midnight that day and nothing is charged. Ending the service has the rest.
When a payment does not go through
When a monthly charge fails, or no payment method is on file when an invoice is issued, Hal warns you each day until the invoice is paid or he pauses. The red badge on Settings → Billing and a banner on the dashboard say what is owed (the invoice and its amount, or the total when more than one is unpaid), why it did not go through, the day Hal pauses and how many days are left, and the owner on your account gets the same notice by email each day.
On Settings → Billing the button reads Update payment method and opens Stripe’s page for it. When you return, the payment is tried at once, and once it goes through the warning clears within a minute. Stripe also retries the invoice on its own.
If it is still unpaid, Hal pauses at the start of the fifth day after the invoice date, in your portal’s time zone. The evaluation’s first invoice has no such grace: its warning is the final-week reminder, so if it cannot be collected, Hal pauses at once.
While Hal is paused
The owner on your account gets one email when the pause begins. Then:
- The portal opens the pause page on every visit, naming what is unpaid. An administrator who signs in is taken straight to Stripe’s page to add a payment method. The payment is tried when they return, and Hal is back within a minute of it going through. Anyone else sees the notice only.
- Chat, in the portal, in Slack and in Zulip, answers with the same notice and does no analysis. What you asked is kept, so Hal has it when he resumes. To cancel instead, reply to the pause email.
- Stopped: collection from Microsoft 365, Google Workspace and the other services Hal reads through their APIs, and triage, investigations, Sentry, watches, Zendesk and Zammad ticket review, the weekly review and the daily digest.
- Still running: logs your Windows endpoints and network devices send keep arriving and are stored, and the collector keeps installing and updating. The daily count of identities and endpoints keeps running, and billing continues through the pause.
When the pause lifts, Hal picks up each source where he left off, as far back as its vendor still holds events: Recovery windows gives each source’s limit, so a long pause can lose events from the sources with the shortest windows. The pause stays on record on the Maintenance page and in the next digest.
Ending the service
An administrator cancels by asking Hal in the portal’s chat. Hal says what cancelling now would mean, including the day the service ends and whether anything more is charged, and records the notice once the administrator confirms. Cancelling is not available in Slack or Zulip, or to anyone who is not an administrator. You can also give notice by replying to any billing email from HAL AI: it counts from the day HAL AI receives it, in your time zone, so a reply that arrives on the evaluation’s last day still ends it with nothing charged.
- During the evaluation, Hal stops at midnight that day, in your time zone, and nothing is charged. The owner on your account gets a short email saying the evaluation is cancelled; if you change your mind or have a question, reply to it.
- After the evaluation, the service ends at the close of the 30th day after the notice, and the final invoice covers through that date, prorated by day. The owner on your account gets an email with the end date, with your billing contact copied. Until then, the status line on Settings → Billing and the dashboard banner give the date, the daily digest carries a SERVICE ENDS line, and an administrator can ask Hal to withdraw the cancellation.
At midnight at the end of the last day, collection and analysis stop and the portal closes. HAL AI deletes the instance and its data within 14 days of the end date. There is no read-only period after it, so download any reports you want to keep before the service ends.
See what Hal surfaces on your own clients.
No deck. Ask us anything first. When you want to see Hal on your own tenants, we sign a short evaluation agreement and stand up your instance; you connect one tenant, Hal watches it for 14 days, and we walk you through what he found.
- 01You ask us your questions. No deck, no demo dataset.
- 02You sign a short evaluation agreement, and we stand up your own instance.
- 03You connect one tenant from your own admin console. Hal watches it for 14 days.
- 04We walk through what he found. Keep going month to month, or revoke the scopes yourself and stop.