BRYTER sells two products built to work together. BRYTER Workflows is an automation platform for legal and compliance teams, built without code, and was the whole company from its founding in 2018. Legal engineers use it to build intake and triage, approval workflows, client portals connected to Microsoft Teams, Slack and email, document automation, contract review, mass claims handling and compliance tools. BEAMON AI is an AI suite for lawyers, sold on its own domain and priced separately.
Assist is a chat assistant that drafts from templates, summarizes and compares contracts against playbooks, translates, and answers from a firm's own knowledge. Extract pulls structured data from large document sets for due diligence, contract review, regulatory reviews and remediation. A plugin brings drafting and redlining into Microsoft Word. Hybrid Agents combine AI and workflow for jobs such as claims processing, timelines from files, court documents, billing guideline review and ISDA review.
BEAMON AI has three published per user tiers and a free trial, and Workflows is quoted. Integrations include SharePoint, Salesforce, DocuSign, iManage, DeepL and the Otto Schmidt legal database. Named customers include Linklaters, Ashurst, Hausfeld, Deloitte, PwC, KPMG, McDonald's, ING Bank, Rakuten and Telefónica. BRYTER GmbH is based in Frankfurt am Main, with offices in London and New York.
Side by side on the same 15 capability axes and 12 legal signals: where the two part company, and what neither one publishes.
Vendors in the same categories as BRYTER whose graded profiles look most alike, with a line on what each product does.
Similar is not the same, so check that each one does the job you need. No vendor pays for placement.
Ordered by how closely the graded profiles match across the 15 capability axes, inside the same categories. See how each axis is graded in the methodology.
All 15 axes, graded from public sources on the date shown. Hover a grade to see what the letter means on that axis.
How much of the product is actually AI. Whether the machine learning is the mechanism the buyer is paying for or a feature layered onto conventional software, and whether the vendor is specific about which is which.
AI drives a core capability on a platform that would still work without it. BRYTER's own formula, on every page, is the power of AI with the precision of workflows, and it names two halves. BRYTER Workflows is a rules based automation platform, built without code, that was the whole company from 2018 and still sells on its own. Without the AI it remains a complete product. BEAMON AI is the AI half and is substantial: three products in Assist, Extract and a Word plugin, its own domain, price list and free trial, and its own place in the agreement's definition of the Software.
BEAMON AI can be bought alone at published per user rates, so a buyer can get the AI without the workflow platform. But BRYTER is both halves: a rules engine with an AI suite alongside it, and increasingly running through it.
Whether the vendor publishes measured accuracy on citations and assertions, grounds output to primary sources, and says plainly what its system does when it does not know. Legal has a documented public record of fabricated citations reaching filed briefs, so an untested claim of accuracy is not evidence.
How answers are grounded is set out, but BRYTER gives no accuracy figure. Hallucination control and references are named as features. Summaries are described as linked to their sources, with citations kept and detail selectable. Assist is described as answering from the customer's own knowledge bank and playbooks. The retrieval sources are named: a web search processor in the subprocessor list and a direct API link to the Otto Schmidt legal database on the top tier.
The agreement adds a frank disclosure. Accuracy may suffer when web search or access to legal sources is not enabled, the service is then more likely to be wrong, and BRYTER recommends turning them on. That tells a buyer when the product gets worse. No accuracy figure, error rate, test set or evaluation is published. The only comparison is unmeasured marketing, that its AI beats generic tools like ChatGPT or Copilot on quality and accuracy.
The agreement is far less confident. It says BRYTER does not guarantee Output is accurate, complete, original, fair, unbiased or free of errors, and where the two differ the agreement governs.
What the system decides on its own, what a lawyer must approve, and whether the vendor documents where the review point sits. A tool that drafts under review and a tool that files without one are different products and different risks.
Human review of the AI's work is a contractual commitment at BRYTER, which also gives real control over which models run. The agreement says the customer must review and validate all results before relying on them for business, legal or other decisions. Using Output without proper human oversight, especially for decisions or compliance, is at the customer's own risk, and Output must be verified before any use. Another clause bars the customer from misleading anyone that Output was written by a person.
The best control is over models. An administrator chooses which language models are enabled for the tenant and can disable any at any time. Within that set, the author picks the model for each input, and both choices count as instructions under the data processing addendum. By default only one model is enabled, and no customer data reaches any other provider until an administrator turns it on. Access is restricted by role, actions are logged and changes can be traced.
What is missing: no published limit says what a given tier's output may not be used for. The commitment is a general promise of human review, plus control over which models run.
Named, dated evidence that the product works in production at real firms or legal departments. Case studies with figures and identified customers count. Unattributed testimonials and launch announcements do not.
Strong customers are named, with no figures attached to any of them. The names span three buyer types: global law firms (Linklaters, Ashurst, Hausfeld), professional services firms (Deloitte, PwC, KPMG) and corporate legal departments (McDonald's, ING Bank, Rakuten and Telefonica). A published customer story covers Telefonica's legal team, and one testimonial carries a named person with title and firm, a counsel and AI expert at REIUS.
No figure is tied to a named customer on the pages read, and nothing is dated. The benefit claims are generic, such as saving hundreds of hours reviewing contracts, with no basis, population or period. Nothing measures BEAMON AI apart from the workflow platform. The customer stories library and the guides and reports section were not opened.
How client confidences are handled: attorney client privilege and work product treatment, segregation of one client matter from another, whether client data trains any model, and what the vendor commits to in writing rather than in marketing.
BRYTER addresses privilege and professional secrecy directly, in documents a buyer can read before signing. The data processing addendum has a section on BRYTER's duty to keep professional secrets, which applies wherever the customer has such duties. BRYTER treats all data as potentially subject to professional secrecy unless clearly determined otherwise. It may learn professional secrets only as strictly necessary, and learning expressly includes any technical or organizational access, whether or not a person reviews it.
It must keep them strictly confidential. It may pass them to subprocessors only where they are contractually barred from passing them on and must flow the duty down, and its own staff must promise in writing not to disclose them. BRYTER also states compliance with German professional rules and the criminal law on professional secrecy, and says it upholds attorney client privilege. Training is banned by contract. Retention is set by data category, with deletion or return at the customer's choice and a limited backup window.
Model providers are named with processing locations, and the default model is stated to run in the EU. Separation is documented through tenant separation and a role concept. One point weighs the other way. The master agreement makes the customer solely responsible for ensuring any Input complies with privilege and professional secrecy duties, so BRYTER protects the material but disclaims the decision to submit it.
Whether the vendor is clear that it supplies a tool rather than legal advice, who its audience is, and how it addresses unauthorized practice of law, competence and supervision duties, and jurisdiction limits. ABA Formal Opinion 512 is the reference point. Where the advice line is not the duty a product raises, the axis is read through the nearest professional duty it does raise: judicial conduct rules and the reviewing duty for products sold only to courts, and the duty to bill for time actually spent for products that draft time entries.
Output is not legal advice under BRYTER's contract, which addresses supervision but sets no jurisdiction limits. The agreement says Output is not legal advice, that BRYTER is not a law firm, does not practice law and gives no legal advice, and bears no legal responsibility for Output or anything derived from it. The usage rules add two less common provisions: a bar on misleading anyone that Output was written by a person, and a bar on giving tailored financial advice without a qualified person reviewing it.
The agreement's review and validation duties cover supervision of legal output. BRYTER also engages professional conduct in at least two countries, mapping its AI suite to named Austrian provisions and stating compliance with German professional rules and the criminal law on professional secrecy. Missing: no jurisdiction limits. Nothing tells a buyer where the product may or may not be used. That matters for a company contracting under German law, selling in the US through a separate entity, in at least three language markets, with added terms for Austrian and Swiss professional secrecy holders. Who may operate the tool is not addressed beyond the license terms Authorized User and Author.
Published governance over model behavior: who owns it inside the vendor, what is tested before release, and what is disclosed about disparate output across matter types, parties, or populations.
A governance framework is written into BRYTER's contract, without test results or a named owner. The master agreement has a dedicated AI Terms section for every AI feature. It bans training on customer content, governs model selection and change, requires human oversight, and sets acceptable use rules. Those rules bar hateful, harassing or violent content, exploiting children, encouraging self harm, misusing personal data, malware, high risk economic harm, health advice, political campaigning and lobbying, and uses that breach privacy or confidentiality.
Bias is addressed in the agreement itself. The customer acknowledges that Output may reflect or amplify biases in training data and agrees to verify and validate all Output before use. Around this sits company governance: ISO 27001:2022 certification, a data protection management system reporting to senior management, records of processing under Article 30, privacy by design training for product teams, and internal and external audits.
Missing: no one is named as accountable for AI, and nothing describes testing before a model or feature ships. No test results are published, and the bias clause is a warning, not a mitigation.
Retention, deletion, access control, and what happens to prompts and documents after they are processed. Whether the vendor states its subprocessors and its incident practice, or leaves the buyer to assume.
Every element of data stewardship is set out, including a subprocessor table. Retention is set by data category: security and audit logs up to ninety days, contact, credential and customer content until termination and then deletion, and backups for thirty days after. On termination BRYTER deletes, or returns and deletes, all personal data and processing results at the customer's choice. There is also a right to switch and port data under the EU Data Act, with a documented process.
Access control is documented under twelve headings. They cover physical access, user and data access, separation, pseudonymization and encryption, input and order control, transmission, availability, resilience, security management, purpose limitation and data protection management. Subprocessors are named with service, company location and server location. Changes need prior written notice with a twenty business day objection right.
Incidents are notified without undue delay, and where feasible within 72 hours, with four required contents. Business continuity, incident response and disaster recovery plans are tested. Two frank disclosures. The addendum discloses monitoring of AI processing, described as LLM observability. And the provider of the chosen language model screens inputs and outputs automatically against its own usage terms, with human review of flagged content case by case.
What the vendor stands behind contractually when its output is wrong. Indemnities, caps, carve outs, insurance, and whether any of it is published or only reachable through a negotiated agreement.
BRYTER publishes real warranties, not only exclusions, but carves the AI out of the strongest ones. It warrants that it can grant the rights, that the Software will be provided with reasonable skill and care and in line with law, that it will materially match the Documentation and the Order, and that functionality will not materially decrease during the term. The remedy is prompt correction or another way to do the task.
There is an uptime commitment backed by a support and maintenance appendix, with response targets of 48 hours standard and 24 hours on the top tier. Liability follows German law. It is unlimited for intent, gross negligence and injury to life, body or health. Slight negligence is limited to breaches of material obligations and capped at the fees for the current subscription period. The catch is the AI. The agreement says support and maintenance apply to the AI Service only to the extent it may have downtime, interruptions and errors, with no guaranteed response or fix time.
It also says BRYTER does not warrant the availability, accuracy or completeness of results from credit based features. So the uptime promise covers the platform, not the models. No indemnity to the customer was found, no insurance is published, and the only indemnities run the other way.
How deeply the product reaches into the systems legal work already lives in: document management such as iManage and NetDocuments, Word and Outlook, contract lifecycle management, matter management, e-billing, and court filing systems.
Integrations are many and come with stated conditions, but BRYTER offers no documentation an implementer could use. Document and knowledge systems: iManage and SharePoint, connecting repositories so precedents appear in context. Business systems: Salesforce and DocuSign. Collaboration: Microsoft Teams, Slack and email as intake channels. Authoring: a Word plugin for drafting, editing and redlining. Publishers and data: a direct API link to the Otto Schmidt legal database, Haufe Lexware, Winsolvenz insolvency software via Septeo, and Handelsregister company data via Company.info.
Language: DeepL, also in the subprocessor list with its processing locations. Platform: BRYTER Connect and an open API, with published API terms, a license to build on it, software kits and code samples. Modules can be triggered from another system and data exported to an internal dashboard. The pricing table states which integrations need the customer's own third party subscription and which are paid extras. Missing: no public API reference or connector list was found, and the help center was not opened. For most connectors nothing says what data moves in which direction or what a firm must set up.
Where the software runs and where the data sits. Multi tenant cloud, single tenant, private deployment, on premises, and whether region of residence is a published option or an enterprise conversation.
BRYTER publishes detailed residency information, but its own documents contradict each other twice on the key point. The pricing table states EU hosting for every tier. The subprocessor schedule gives a server location for each party: cloud hosting in Frankfurt, the default language model hosted by Microsoft Azure in the EU, and other named locations. A clause says that by default only one model is enabled, processed within the EU, and that no customer data goes to another model provider until an administrator enables it.
Tenancy is covered by the Tenant concept in the agreement and by documented separation of customer data into separate systems. So a buyer is told both where data is stored and where AI processing happens. The contradictions are not resolved in BRYTER's favor. First, within the data processing addendum, the subprocessor schedule lists servers in Frankfurt, the EU, Sweden and the Netherlands. But the technical measures schedule says all personal data is stored and processed in US data centers of AWS and Microsoft Azure.
Second, the security page says customer data, prompts and outputs never leave the EU and EEA, but the schedule lists an optional model provider and a web search processor with servers in the USA. A buyer cannot reconcile these from what is published.
Independent attestation a buyer can pull without a sales call: SOC 2, ISO 27001, penetration test summaries, a trust center with current reports and named scope rather than a badge image.
Current certifications are named precisely by BRYTER, but the route to evidence is broken. It claims SOC 2 Type II and ISO/IEC 27001:2022, with the version year, on the pricing table against every tier and on the security page. The data processing addendum records internal and external ISO 27001 audits, sets out technical and organizational measures under twelve headings, and names the certifications of its two cloud subprocessors.
Missing: no auditor is named, no report period or certificate number is published, and the trust center was not reached. The pricing table links to a trust center at trust.bryter.io, which returns a 404 error, while the security page links to trust.bryter.com. That working address was found but not opened.
Which models sit underneath, whose they are, where they run, and whether the vendor commits to telling customers when that changes. A legal buyer inherits every dependency it cannot see.
Model providers are named, and customers control which ones run, but BRYTER names no model. The agreement and subprocessor schedule identify Microsoft Azure as the cloud host of the default language model, and Anthropic Ireland as an optional model used only when a customer administrator enables it. A web search processor is named for the AI suite, and the usage restrictions also name OpenAI and Azure OpenAI among the third parties providing the AI Service.
Each has a company location and a server location. Change notice is a real process: prior written notice before adding or replacing a subprocessor, a twenty business day objection right on material grounds, and a defined result if the objection stands. Customers control which provider handles what at two levels: administrators enable providers per tenant, and authors choose per input. No model is named anywhere. The pricing table says only that available models are updated continuously.
The agreement lets BRYTER add, replace, upgrade or drop models at any time, with no customer claim to any specific model or version. A buyer knows whose infrastructure runs the AI, but not which model is answering.
Whether a buyer can learn what this costs without entering a sales process: published rates, the unit being charged, what sits behind an enterprise tier, and what implementation adds.
A buyer can price BRYTER's AI suite to the euro without speaking to anyone, and can read the contract terms behind it. Rates are per user per month. Single is 99 euros annual or 118 euros monthly, for solo practitioners without team features. Team is 149 euros annual or 176 euros monthly, adding shared projects, documents and grids with a central prompt library. Pro is 199 euros annual or 234 euros monthly, adding workflow automation, single sign on, integrations and priority support.
Both billing options are shown, so the annual discount can be worked out. A comparison table of about eighteen rows covers features, integrations and publishers, and compliance and support. It marks which integrations need the customer's own third party subscription and which are paid extras. Purchase is self serve, with a free trial and sign up, and published terms for buying through Stripe. The agreement also publishes terms buyers usually find later.
These include annual invoicing in advance, yearly increases capped at ten percent, ninety days' notice and a right to leave if fees change at renewal, and thirty days' notice for credit rate changes. There is a monthly credit cap with unused credits forfeited, a token limit with notice at eighty percent, thirty day payment terms and a stated late payment interest rate. Two limits. BRYTER Workflows is not priced publicly and is quoted, and premium model access may cost extra under the Order.
Who the product is actually built for. AmLaw, midlaw, small firm and solo, in house departments, government and courts, and which practice areas are supported rather than merely claimed.
Coverage spans segments and tasks, with no limits stated by BRYTER. Law firms and corporate legal teams each have their own solution pages and use cases. The customer list shows all three buyer types BRYTER claims: global law firms, professional services firms and corporate legal departments. Firm size is covered by the pricing tiers, described by type of practice. The entry tier is for solo practitioners without team features, the middle tier for teams that share projects and prompts, and the top tier for firms and legal departments needing a full enterprise setup.
Tasks are listed in a library of about twenty use cases, from clause extraction and contract review to due diligence, discovery summaries, litigation and matter summaries, horizon scanning, invoice summaries, redlining and NDA generation. Reach across countries shows indirectly, through English, German and Spanish sites, German and Austrian legal database links, and added terms for Austrian and Swiss professional secrecy holders.
Missing: nothing names a practice area or firm type the product is not for, nothing covers government use, and jurisdictions are left to be inferred rather than stated.
The public pages on file for BRYTER, with the recorded signals each one supports and the date it was last read. Open any of them and check the reading against the record.
Prompt and Output Retention, Ethical Walls and Matter Segregation, Outside Counsel Guideline Readiness
Read Sep 12, 2026
Client Data in Training, Third Party Request and Subpoena Notice, Refusal and Uncertainty Behavior
Read Sep 12, 2026
Good Law Verification, Court Disclosure Support
Read Sep 12, 2026
Bar Guidance Alignment
Read Sep 12, 2026
Primary Law Corpus Provenance
Read Sep 12, 2026
Billing and Fee Posture
Read Sep 12, 2026
Three published tiers for BEAMON AI, priced per user per month in euros, with monthly and annual rates shown. Single is 99 euros annual or 118 euros monthly, only for solo practitioners and without team features. Team is 149 euros annual or 176 euros monthly, for teams that need shared projects, documents and grids with a central prompt library. Pro is 199 euros annual or 234 euros monthly, for firms and legal departments needing a full enterprise setup with workflow automation, integrations and priority support.
Every tier includes unlimited AI chats, Assist, the Word plugin, Extract and continuously updated models. Team adds shared profiles and the prompt library. Pro adds published workflows, single sign on and the Otto Schmidt API. The comparison table runs to about eighteen rows and states the condition for each integration. Otto Schmidt and Haufe Lexware need the customer's own subscription, Winsolvenz needs a Septeo subscription, and Handelsregister company data and DeepL translation are paid extras.
Support response is 48 hours standard and 24 hours on Pro. Purchase is self serve, with a free trial and sign up, and published terms for buying through Stripe. The master agreement sets out the mechanics. Fees are invoiced yearly in advance. Yearly increases must be in good faith, in line with cost increases, and capped at ten percent. Fee or usage limit changes at renewal need ninety days' notice and give the customer a right to terminate.
Credit rate changes need thirty days' notice. Credit based features have a monthly credit cap, with unused credits forfeited at month end and suspension when credits run out. AI connectors have a limit of ten million tokens per tenant per month, with notice at eighty percent. Payment is due in thirty days, with interest at six percent a year on late payment, and termination before a renewal term needs ninety days' notice. A discount tied to bar association membership is named.
Confidentiality and data terms: No business associate agreement is offered and none would be expected: this is a German-contracting vendor selling to legal and compliance teams in Europe and the United States, and HIPAA is addressed nowhere on either estate. What stands in its place is a fuller European instrument set than any record in this corpus, and it is published rather than offered on request. Data processing addenda exist in two regional versions, Germany and EMEA and a separate United States version contracted through BRYTER US Inc., each versioned in parallel with the master agreement and each carrying a sub-processor schedule with server locations and a twelve-heading schedule of technical and organisational measures. A CCPA addendum is published for United States customers. The addendum carries a dedicated professional secrecy section for customers subject to statutory confidentiality duties, expressly extending to legal, tax and healthcare professionals, which is the nearest functional analog to a BAA on this estate and is graded on the privilege row. Certifications claimed first-party are SOC 2 Type II and ISO/IEC 27001:2022; no auditor, report period or certificate number is published and the trust center was not opened.
Note: Figures and tier contents read from BRYTER's open pricing table on 12 September 2026, at beamon.ai/pricing via bryter.com/pricing/aisuite/, page last modified 4 September 2026. Commercial terms read in full from the Master Service Agreement (German law) version 11.0, August 2026, published with a history of seventeen versions back to November 2022 and a PDF download. All figures are in euros, and the entry price is shown in euros: 99, the lowest published paid rate, for the Single tier at 99 euros per user per month on an annual plan. Third party sites quoting the same tiers in US dollars were found and not used. Two limits. These rates cover BEAMON AI only, and BRYTER Workflows is not priced publicly, so a buyer wanting it is quoted. And the agreement says premium models may carry extra fees or limits set in the Order, the pricing page or the documentation, so the top of the range is not fully known in advance. BRYTER's own footnote says the table is an overview only, with exact scope governed by the published BEAMON Service Description.
BRYTER released BEAMON 2.0, which adds an agentic mode in which the assistant plans a multistep task, pulls information from several sources and works through it to completion, such as drafting a long pleading to a detailed specification or researching across many documents. The release also adds Projects, which group chats, folders and documents by client, matter or topic.
A signal records what public sources say on the date shown. It is not a grade and it is not a recommendation. Where a signal reads Not addressed, it means the index did not locate the material in public sources on that date, which is a statement about disclosure rather than about the product.
Can material a lawyer puts into this product be used to train a model?
The published terms prohibit training on customer content. Not a policy page, the agreement.
BRYTER's master agreement bans training on customer content. Its AI Terms section has a heading that says Customer Input will not be used for AI Training. The clause says BRYTER does not use Customer Content to train machine learning models, and that using the AI Service gives BRYTER no right or license to train on Customer Content. That second part closes off training by license as well as in practice. A separate clause licenses BRYTER to use Customer Data only to provide the software, which is therefore not a training license.
The ban is repeated on the pricing table for every tier and on the security page, which says customer data, prompts and outputs are never used to train AI models. The agreement is published, versioned and matches the marketing. The only exception: BRYTER may use data from the customer's use of the AI Service where the customer volunteers feedback or gives permission. Two further points. The customer may not use the AI Service to build competing foundation models.
And the addendum discloses that the chosen model provider screens inputs and outputs automatically, with human review of flagged content case by case. That is not training, but a third party may read customer content.
How long does the product keep what a lawyer typed, and can that be set to zero?
A specific retention period is published and the customer cannot change it.
BRYTER states retention periods category by category. A table in the data processing addendum gives purpose and duration for each type of data. Contact and account data and login credentials are kept until termination. Network and device identifiers, log files and audit trails are kept up to ninety days where applicable, otherwise until termination. Customer content, defined to include uploaded documents, free text, extracted fields and AI output containing personal data, is kept until termination and then deleted.
On termination BRYTER deletes, or returns and deletes, all personal data and processing results at the customer's choice, with backups allowed for thirty days under the addendum. So a buyer can trace a prompt from submission to deletion. Two frank disclosures in the same table qualify this. Data is also used for quality assurance, error analysis and monitoring of AI processing, described as LLM observability. And the provider of the chosen language model screens inputs and outputs automatically against its usage terms, reviewing flagged content case by case. No shorter retention window at the model layer is published.
Does retrieval respect the firm’s ethical walls, or can the model read across them?
The product maintains its own permission model, documented, requiring the firm to keep it aligned.
A permission model of BRYTER's own is set out in its technical and organizational measures. Customer data is kept strictly separate, in separate systems, from BRYTER's own data, and customer data, test data, contact data and employee data are separated from each other. Rights management is central and split between system and application access. Users cannot change their own rights, and rights changes need approval. A role concept with phased access rights is based on identity management.
The agreement supports this. Each Authorized User needs an individual login, account sharing is banned, reassignment is restricted, users may only act within their assigned roles, and BRYTER has an audit right. Projects let users organize chats and documents by case. BRYTER integrates with iManage and SharePoint, but nothing says it enforces those systems' access rules per user at query time. Keeping the two aligned is the firm administrator's job. No conflicts or ethical wall feature is named.
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
Terms commit to notice where lawfully permitted. No transparency report located.
Notice of compelled disclosure is a BRYTER commitment in two forms, with no transparency report. The master agreement allows disclosure under a valid order of a court, government or regulator, or as law requires. The receiving party must promptly tell the other party and let it object or seek a protective order, as far as the law allows. That is notice plus a chance to resist. The data processing addendum adds a second commitment for physical seizure.
If personal data in BRYTER's control is subject to search and seizure, attachment, confiscation in insolvency or similar measures, BRYTER must tell the customer without undue delay. It must also tell all parties that the data belongs solely to the customer, who is the responsible party. A third clause says that if law requires processing outside the customer's instructions, BRYTER must tell the customer first, unless the law forbids it on important public interest grounds. No transparency report, schedule or aggregate figure was found.
Where does the law in this product come from, and does the vendor have the right to use it?
The vendor names its primary law sources and the license or public domain basis for each, with an update cadence.
Each content source is named with its rights basis, but BRYTER builds no legal corpus of its own. Instead it connects to named outside sources, with licensing stated on the pricing table. The Otto Schmidt legal database is reached by direct API on the top tier and needs an existing Otto Schmidt subscription. Haufe Lexware needs an added Haufe subscription on every tier. Handelsregister company data via Company.info and DeepL translation are paid extras, and DeepL also appears in the subprocessor list with its processing locations.
Separate terms are published for the Otto Schmidt Legal Data Hub. So the rights basis is that the customer brings its own license, a clear answer even though it shifts the duty rather than taking it on. Two limits. The web search feature runs through a named third party search processor, with no stated basis for what it retrieves. And nothing says what the language models were trained on, and the agreement reserves the right to change models at any time.
Does the product tell you when the authority it just cited has been overruled?
No located public material addresses whether authority is checked for subsequent history.
No check of legal authority for later treatment comes with BRYTER. It is a contract and workflow product first. Its use case library covers clause extraction, contract review and drafting, due diligence, document comparison, redlining, NDA generation, timelines and obligation tables, with legal research as one item of about twenty. Research runs through a licensed publisher's database the customer subscribes to separately, and any currency signals there are the publisher's, not BRYTER's. Nothing describes flagging overruled, superseded or negatively treated authority, and no citator is claimed.
Summaries keep citations attached, which shows where text came from, not whether the law is still good. The agreement says accuracy may be lower when access to legal sources is not enabled, which ties currency to a setting without describing any check. Pages read on the date shown: the security page, the pricing comparison table, the product and use case pages, and the AI Terms section of the master agreement.
What does the product do when the answer is not in the corpus?
No located public material addresses what the product does when it cannot ground an answer.
When the system cannot give a reliable answer, nothing says what it does, though BRYTER comes close. Hallucination control is a named feature on the security page but is never described: no abstention, confidence signal, threshold or handling of unclear input. A feature title is not a description. What the agreement does publish is when accuracy drops. The customer accepts that Output may be less accurate and reliable if web search or access to legal sources is not enabled, that the service is then more likely to be wrong, and that BRYTER recommends enabling them.
That is honest, but it describes a setting, not the model flagging doubt as it answers. The rest is disclaimer. BRYTER does not guarantee Output is accurate, complete, original, fair, unbiased or free of errors, and the customer must verify all Output before use. In practice, an Extract user running a large due diligence set is told to check everything, but not which extractions the system was least sure of.
Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?
No court order, opinion or disciplinary record addressing fabricated or hallucinated legal citations produced by this product has been located as of the date shown. This is a statement about the public record on that one subject, not a finding about the product, and this signal is not a litigation history.
Searched on 12 September 2026, on the company name and the AI suite name, across published trackers and coverage of decisions on fabricated citations produced with AI. That included coverage of the Damien Charlotin database, reported as listing more than 1,353 affected filings worldwide, and reporting on 2025 and 2026 sanctions decisions in US federal circuits and state appellate courts. None located. This check covers fabricated citations only, so it is not a litigation history and other proceedings would not appear here.
The risk arises where a product generates legal authority for filing. BRYTER centers on contract review, extraction, drafting from the customer's own templates and workflow automation. Research against a licensed publisher database is available on the top tier, so the risk is real but narrower than for a research platform.
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
Public materials engage with at least one named ethics opinion.
BRYTER names professional guidance and maps its product to it. On a dedicated page, BRYTER says BEAMON AI meets the data protection and professional law rules for Austrian lawyers, and names them: section 9 of the Rechtsanwaltsordnung, section 40 paragraph 3 of the RL-BA 2015, and the GDPR with the Austrian Data Protection Act 2018. It explains how, citing unlimited confidentiality, a processing agreement under Article 28 GDPR, EU data processing and an express ban on training AI models with customer data.
It says it has fully completed and signed, at company level, the Austrian Bar Association's checklist for AI providers, and that added provisions for Austrian professional secrecy holders apply. Those provisions are published as a standing document in its legal terms. Germany is covered more briefly. The security page states compliance with the BRAO and section 203 of the Criminal Code, and the agreement offers a discount tied to bar association membership.
The Austrian material is a real mapping. The German material asserts compliance and names the rules without mapping them. The published notes for Swiss and German professional secrecy holders were not opened.
Does the vendor address what happens to the bill when the work takes an hour instead of six?
Public materials claim time savings without addressing billing or disclosure, and the product sits inside a fee relationship between a lawyer and a client where those savings would change the bill.
Time savings are the claim, the product sits inside the fee relationship, and nothing addresses billing or disclosure. The claims are clear: save time and reduce costs, save hundreds of hours reviewing contracts, free legal teams from repetitive tasks, and speed up work that took thousands of hours of manual review. Buyers include global law firms that bill those hours to clients, so this is BRYTER's own selling point.
Nothing addresses what happens to the bill. There is no per matter record of AI work, nothing marks output as machine produced for fee purposes, and no fee or disclosure guidance appears, even in a detailed agreement of sixteen sections with its own AI terms. Two features touch invoices but are not records of AI work: a billing guidelines agent that reviews and corrects invoices and matter descriptions, and an invoice summary use case. One usage rule points this way: a contractual bar on misleading anyone that Output was written by a person.
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
A subprocessor and model provider list plus client facing disclosure material is published or available without an agreement in place.
All three items a firm would forward are available without an agreement or request. Schedule 1 of the data processing addendum lists each subprocessor with its service, company location and server location: cloud hosting in Frankfurt, a monitoring tool, a file conversion processor, a translation provider and a web search processor. The same table names the model providers. Microsoft Azure hosts the default language model in BEAMON, and Anthropic Ireland is an optional model used only when a customer administrator enables it.
A firm asked which third party sees its client content can answer by name, role and location, and say which are on by default and which need its own action. The addendum itself is the client facing document, drafted to be handed to a client. Subprocessor changes need prior written notice with a twenty business day objection right. Two further points. The addendum bars subprocessors from passing on professional secrets. And a completed bar association checklist for AI providers exists in one country as a forwardable document.
If a judge’s standing order requires an AI disclosure, can the product produce one?
No located public material addresses court disclosure or verification certification.
Disclosure of AI involvement in legal work has no BRYTER feature behind it, though two things come close. The security page says access is limited by role and need, actions are logged and changes traceable, and lawyers stay responsible for decisions, with audit trails supporting internal governance and external requirements. But nothing says the trail shows which passages a model wrote, separates machine drafted from human edited text, survives export, or could be put before a tribunal.
It reads as a security log, not a disclosure record. The second is a usage rule: the customer must not mislead anyone that Output was written by a person. That is a duty of candor on the customer, not a feature that makes candor possible. There is no disclosure template, certification, model identifier on output, or export built for filing. This matters because BRYTER's agents handle court documents and claims, so output does get near a tribunal. A firm later asked which parts of a filing a model drafted would have nothing published to work from.
Every grade and every signal on this index is drawn from public sources and dated. If a record is wrong, out of date, or missing an artifact the index did not locate, send the source and it will be reviewed and the record redated. Vendors are welcome to submit documentation. Nothing on this index is for sale, including a listing, a placement, or a grade.