Aloy

Aloy (usealoy.com) is a customer workspace for business-to-business teams, combining support, customer success, and account intelligence in a single tool organised around accounts rather than tickets¹. The product is operated from Hannover, Germany, under the name Aloy Technologies, with Serkan Şentürk named in the site imprint as the responsible person²³. It is hosted in the European Union, with data processed in Frankfurt am Main⁴. As of August 2026 Aloy is in a free early-access phase, onboarding a selected group of B2B teams with setup handled jointly by the company⁵. The site is published in English and German¹.

Product

Aloy organises customer work by account instead of by ticket queue. Conversations arriving through any channel are matched to an account, and the account carries its own history, ownership, and health¹. The product is presented as three jobs sharing one workspace¹.

Support

Aloy answers customers in the channels they already use, naming Slack, Microsoft Teams, WhatsApp, email, and in-app chat⁶. An incoming message is matched to the right account and routed to the right team. Replies happen against a shared board with views and filters by owner, team, account, and status, and the account history including past issues and open promises is shown alongside the conversation⁶. The company frames its use of AI as assistance rather than replacement, describing the goal as better tools for the people who work with customers⁶.

Success

Aloy derives account health from conversations rather than product usage alone. It scores vibe and risk for each contact, weights those signals by the contact’s role, and rolls them up into an account-level health figure⁷. The stated premise is that a quiet account is not automatically a healthy one, and that health should move when a champion sounds frustrated or a decision maker cools off, ahead of the renewal call⁷. Account owners are notified when the relationship changes⁷. Zapier, Make, and an in-app live-chat widget are named as integrations⁷.

Intelligence

The intelligence module summarises what is happening inside an account and what patterns are forming across the customer base, with sources attached to each key signal⁴. It surfaces feature requests spotted across channels so demand is visible rather than anecdotal, and detects anomalies across accounts and themes⁴.

Pricing

Aloy is free during early access, which the company describes as open to a selected group of B2B teams⁵. Paid packages have been announced but not released:

Plan	Status	Price
Early Access	Open now	Free5
Starter	Not yet released	Expected from 69 EUR per user per month5
Professional	Not yet released	Expected from 99 EUR per user per month5
Enterprise	Available	Custom, billed yearly5

The Enterprise plan adds SSO and SAML, a custom SLA, and on-premise or self-hosted deployment⁵. Early-access teams are promised the best terms on whichever plan fits when packages are set, and onboarding is done jointly on a call using the customer’s real accounts and channels⁵.

Hosting and data residency

Aloy states that it is hosted in the European Union, with data processed in a private cloud environment in Frankfurt am Main, Germany, and describes itself as GDPR-compliant by default⁴. On-premise and self-hosting options are offered on request⁴⁵.

Who it’s for

The company describes its early-access candidate as a B2B team of 50 to 500 people, or a startup wanting a strong customer experience from the start, whose customer communication is currently spread across shared Slack channels, Zendesk, Intercom, CRM notes, spreadsheets, or Notion, and where account context is still assembled by hand⁸.

How it compares

Product	Starting price	Channels	Unit of work	Conversation-based health
Aloy15	Free in early access, from 69 EUR/user/mo expected	Slack, Teams, WhatsApp, email, in-app chat6	Account1	Yes, vibe and risk per contact7
Pylon9	Not public	Slack, Teams, email, chat widget, HubSpot, Salesforce9	Account	Not stated9
Zendesk10	USD 55/agent/mo (Suite Team, annual)	Multichannel suite	Ticket	No
Intercom11	USD 29/seat/mo (Essential), Fin at USD 0.99 per outcome	Chat-led multichannel	Conversation	No
Vitally12	Not public, quote on request	Not a support inbox	Account	Usage-led, not conversation-led12

Pylon positions itself as an agentic support platform and does not publish prices, listing a demo booking instead⁹. Vitally is a customer success platform rather than a support tool, and also quotes on request¹².

Alternatives

• Choose Pylon for B2B support in shared Slack and Teams channels from an established vendor with CRM integrations, if a sales conversation to reach pricing is acceptable⁹.
• Choose Zendesk for a mature, broad support suite with published per-agent pricing, where a ticket-centred model fits the workflow¹⁰.
• Choose Intercom for chat-led support with the lowest published entry seat price and per-resolution AI pricing¹¹.
• Choose Vitally if the requirement is customer success and account health on its own, separate from a support inbox¹².
• Choose Aloy for an EU-hosted single workspace where support, success, and intelligence sit on one account record, where account health is derived from what customers actually say rather than from usage counters, and where the future price is published up front instead of quoted on a call¹⁴⁵.

Company

Aloy Technologies is based in Hannover, Germany, with Serkan Şentürk named in the imprint as the responsible person and the business operating under his name²³. The published contact email is hello@usealoy.com².

The company writes publicly about the problem it is building against, with a blog beginning in July 2026 that argues B2B support breaks because it is organised around queues rather than accounts¹³. It is currently recruiting founding customers, listing three open slots, and has not yet published customer stories, so the accounts shown in the homepage product tour are illustrative rather than a customer roster¹⁸.

Recent activity

• August 7, 2026. Published “How to spec AI triage when support lives in shared channels,” on configuring AI triage for shared Slack and Teams channels using account context¹³.
• July 10, 2026. Published “Your B2B support setup is messy because it is built around queues,” arguing that queue-based and channel-based organisation breaks down when the relationship sits at the account level¹³.
• July 10, 2026. Published “Keep the shared Slack and Teams channels. Make them scale,” on adding memory, ownership, and account context to shared customer channels¹³.

External links

• Official website
• Pricing
• Customers
• Blog

Footnotes

1. Aloy homepage. Retrieved August 10, 2026. https://usealoy.com ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷ ↩⁸

2. Aloy Imprint (English). Retrieved August 10, 2026. https://usealoy.com/en/imprint/ ↩ ↩² ↩³

3. Aloy Impressum (German). Retrieved August 10, 2026. https://usealoy.com/de/impressum/ ↩ ↩²

4. Aloy Intelligence page. Retrieved August 10, 2026. https://usealoy.com/en/intelligence/ ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶

5. Aloy Pricing page. Retrieved August 10, 2026. https://usealoy.com/en/pricing/ ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷ ↩⁸ ↩⁹ ↩¹⁰ ↩¹¹

6. Aloy Support page. Retrieved August 10, 2026. https://usealoy.com/en/support/ ↩ ↩² ↩³ ↩⁴

7. Aloy Success page. Retrieved August 10, 2026. https://usealoy.com/en/success/ ↩ ↩² ↩³ ↩⁴ ↩⁵

8. Aloy Customers page. Retrieved August 10, 2026. https://usealoy.com/en/customers/ ↩ ↩²

9. Pylon pricing and demo page. Retrieved August 10, 2026. https://www.usepylon.com/pricing ↩ ↩² ↩³ ↩⁴ ↩⁵

10. Zendesk pricing page. Retrieved August 10, 2026. https://www.zendesk.com/pricing/ ↩ ↩²

11. Intercom pricing page. Retrieved August 10, 2026. https://www.intercom.com/pricing ↩ ↩²

12. Vitally pricing page. Retrieved August 10, 2026. https://www.vitally.io/pricing ↩ ↩² ↩³ ↩⁴

13. Aloy blog index. Retrieved August 10, 2026. https://usealoy.com/en/blog/ ↩ ↩² ↩³ ↩⁴