Neuroflash
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by neuroflash GmbH · neuroflash.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Neuroflash at a glance
- Vendor
- neuroflash GmbH
- Headquarters
- Not stated on the vendor’s pages as of 17 Nov 2026
- Data hosting
- Default not stated; pages mention Germany source, captured 17 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 17 Nov 2026
- Panel verdict
- The AI panel rates Neuroflash 2/5, the mean of 6 judges. neuroflash GmbH of Hamburg sells an AI content marketing suite — content editor, brand hub, 100+ templates, SEO and GEO optimisation, workflows, team collaboration. how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 19 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
neuroflash GmbH of Hamburg sells an AI content marketing suite — content editor, brand hub, 100+ templates, SEO and GEO optimisation, workflows, team collaboration. The strongest criterion, distribution and integrations at 6, rests on a versioned API with a public changelog, 88 endpoints across 7 domains, published rate limits (60 requests per minute on Developer, 600 on Scale), a hosted MCP server and a 99.9 percent SLA from Scale. Editorial planning and collaboration and approval both sit at 2: we found no public information on calendars, owners, due dates, comments, version history, approval steps or an audit trail. Pricing transparency is 4 — a free tier with 5,000 credits per day, pay-as-you-go at Ab 0,20 € pro 1.000 Credits, no public price for the Scale plan or seat-based team plans, Enterprise by individual quote. Sovereignty spans 6 to 7, AI and content rights 5 to 6, content model and reuse 2 to 3; no flagged split was recorded, the one-point spreads turning on the USA share of AI processing and on retention, output ownership and a data processing agreement left undocumented.
Speaks for it
- A versioned API with a public changelog, OAuth 2.0 with PKCE, published rate limits (60 requests per minute on Developer, 600 on Scale, custom on Enterprise) and 88 endpoints across 7 domains.
- A free start with 5,000 credits per day, self-serve and no subscription, alongside pay-as-you-go at Ab 0,20 € pro 1.000 Credits and published per-output costs — blog article 20 CU, social media post 5 CU, AI image 6 CU, twin query 6 CU.
- A Hamburg-registered contracting entity — neuroflash GmbH, Amtsgericht Hamburg, HRB 117450 — with a named data protection officer in Hamburg and ISO 27001 certification.
- Stated EU hosting on Google Cloud Platform and at Raidboxes in Germany, with subprocessors published with country, purpose and transfer basis (Stripe and Stape in the USA, Usercentrics in Munich).
- Stated training exclusion — inputs never train public models and brand voice, guidelines and documents are not used for training — with the models GPT, Gemini, Claude and Mistral named.
Held against it
- We found no public information on an editorial calendar, owners, due dates or briefs that carry goal, audience and keywords to the writer.
- We found no public information on comments, version history with restore, roles separating writing from publishing, or an audit trail of who released which version.
- We found no public information on a configurable content model, locales managed side by side, or a documented export of content, model and assets.
- We found no public information on webhooks, SDKs or named connectors into the CMS, CRM and analytics tools a marketing stack already runs.
- We found no public information on prompt and output retention, ownership of generated output in the terms, EU AI Act labelling, or a data processing agreement.
Best for
- You want to prototype AI content generation before committing budget — Developer is free with 5,000 credits per day, self-serve, no subscription.
- Your team writes in a defined brand voice across channels and wants voices, documents, target audiences and knowledge stored centrally and applied automatically to every piece.
- You build with Claude Desktop, Cursor or Windsurf and want a hosted MCP server on a versioned, publicly documented API.
- You are a European buyer who values a German contracting entity and EU hosting on named infrastructure, accepting the stated processing of AI queries in the EU and in the USA.
Avoid if
- You require AI processing to stay within the EU — the captured pages state that AI queries run in the EU and in the USA on servers of external providers.
- Your published content is a legal statement and you must produce an approval trail showing who released which version — we found no public information on approval steps or an audit log.
- You need approved drafts pushed into your existing CMS, CRM or analytics stack — the documented API domains are generation-side and we found no public information on connectors or webhooks.
- You must budget an annual team cost without a sales conversation — we found no public prices for the seat-based plans or the Scale plan, and Enterprise is an individual quote.
The scores
| Criterion | Panel median |
|---|---|
| Planning, editorial calendar & briefs | 1 of 5 |
| Creation, review & approval | 1 of 5 |
| Structured content, localisation & export | 1.5 of 5 |
| Publishing, distribution & integrations | 3 of 5 |
| AI assistance & content rights | 3 of 5 |
| European sovereignty | 3.5 of 5 |
| Pricing transparency | 2 of 5 |
Planning, editorial calendar & briefs
Show reasoningHide reasoning
How this is scored
Turning a content strategy into scheduled work: topics and campaigns, an editorial calendar across channels, briefs that carry the goal, audience and keywords to the writer, and a view of what is due, late or missing.
0 — No planning at all; the product only stores or renders content.
3 — A calendar or list view of content with publish dates and statuses.
5 — An editorial calendar across channels with owners, due dates and custom statuses, and content grouped by campaign, topic or channel.
8 — Strategy connected to the plan: briefs carrying goal, audience and keywords attached to each piece, topics or personas defined once and assigned to pieces, configurable workflows per content type, workload and deadline views per person, and recurring formats scheduled as series.
10 — The plan is accountable: every published piece traces back to its brief, topic and campaign, gaps in coverage per topic or funnel stage are reported, and plan-versus-published is visible over time without a spreadsheet.
The Head of Content
The captured pages name a workflows module and a "complete blog workflow" with keyword analysis and a content score, plus a brand hub that stores target audiences and applies them to every piece of content. We found no public information on an editorial calendar, owners, due dates or custom statuses, and none on briefs that carry the goal, audience and keywords to the writer. 5 8
The SME Marketer
The captured pages list a workflows module and a complete blog workflow with integrated keyword analysis and a content score, and that is where my planning evidence ends. We found no public information on an editorial calendar, owners and due dates, briefs carrying goal and audience, or content grouped by campaign. 5 8
The Localisation Lead
The captured pages name a workflows module and a blog workflow with integrated keyword analysis, but we found no public information on an editorial calendar, briefs carrying goal and audience, owners, due dates or content statuses. What is documented is content production assistance, not a plan a team can be held to. 5 8
The Web Engineer
The captured product pages name a workflows module and a complete blog workflow with integrated keyword analysis and a content score, but they show no editorial calendar, no due dates or owners, and no briefs or campaign grouping. It presents as a generation tool rather than a planning system. 5 8
The Data Protection Officer
The captured pages name a content editor, more than one hundred templates, keyword analysis, a content score and a blog workflow — strategy inputs such as brand voice and target audiences sit in the Brand Hub, but nothing ties them to scheduled work. We found no public information on an editorial calendar, owners, due dates, custom statuses, briefs carrying goal and audience to the writer, or content grouped by campaign. As far as the evidence goes this is a generation and optimisation suite, and the plan-versus-published question a marketing lead would ask is not addressed on any page we read. 5 8
The Skeptic
The captured pages show a complete blog workflow with keyword analysis, a content score, 100+ templates and SEO/GEO optimization, but we found no public information on an editorial calendar, briefs carrying goal and audience, owners, due dates, or grouping by campaign or channel. Strategy inputs like keywords exist; the schedule itself is nowhere documented. 5 8
Creation, review & approval
Show reasoningHide reasoning
How this is scored
Writing and reviewing content together: editing with comments and suggestions, roles and permissions for internal and external contributors, and an approval trail that records who released which version — published content is a legal statement (UWG, Heilmittelwerbegesetz, the imprint duty).
0 — A single-user tool; content cannot be shared with or reviewed by others.
3 — Several users working on content, with comments or a version history.
5 — Roles and permissions that separate writing from publishing, comments on content, a version history with restore, and an approval or review status before publishing.
8 — Configurable multi-step approval per content type or market, mandatory reviewers (legal, product, brand), inline suggested edits, guest or freelancer access limited to assigned pieces, scheduled publishing that waits for approval, and an audit log of every edit, approval and publish with user and timestamp.
10 — Approval is evidence: the exact version each approver released is preserved and exportable, permissions reach down to field and locale level, and the audit trail is retained for a stated period and available after the contract ends.
The Head of Content
Team collaboration in 30+ languages and a brand hub applied "regardless of who is creating in the team" show several people creating together. We found no public information on comments, version history with restore, roles separating writing from publishing, or an approval trail recording which version legal released — the first thing I would have to produce when a published claim is challenged. 5 8
The SME Marketer
Team creation is confirmed — the brand hub applies brand rules to every piece "regardless of who is creating in the team", and the vendor counts over 150 enterprise customers. Beyond that we found no public information on comments, version history, roles separating writing from publishing, approval steps or guest access for an agency. 5 8
The Localisation Lead
Team collaboration and a Brand Hub that applies brand voice, audiences and knowledge to every piece regardless of who creates in the team are documented, so several people do work on content together. We found no public information on comments, version history with restore, roles separating writing from publishing, approval steps or an audit trail — the approval question a German marketing team needs answered for UWG and imprint duty is simply not addressed. 5 8
The Web Engineer
Team collaboration is a named module, the Brand Hub applies brand rules regardless of who is creating in the team, and the Enterprise plan targets teams and agencies, so several people clearly work on content together. The captured pages show no roles separating writing from publishing, no comments, version history or restore, and no approval trail recording who released which version — which matters because published content is a legal statement. 5 7 8
The Data Protection Officer
Team collaboration and "workflows" are named among the modules, and the Brand Hub applies brand rules "regardless of who is creating in the team", so several people evidently work on content together. We found no public information on comments, a version history with restore, roles separating writing from publishing, multi-step approval with mandatory reviewers, or an audit log of who released which version — the release trail I require before signing content off as a legal statement. What the "workflows" actually govern is not specified on the pages we read. 5 8
The Skeptic
Team collaboration is confirmed — workflows and team collaboration in 30+ languages, with brand rules applied automatically regardless of who creates — but we found no public information on comments, version history with restore, roles separating writing from publishing, approval steps before release, or an audit log. For content that is a legal statement, nothing on these pages records who released which version. 5 8
Structured content, localisation & export
Show reasoningHide reasoning
How this is scored
Whether content is stored as reusable structure rather than pages: a content model, components shared across channels, German and other locales managed side by side, and the whole repository exportable in a documented format.
0 — Not a content store; the product keeps no content of its own (for example a pure scheduling or analytics tool).
3 — Templates or custom fields for content, a media library, and content in several languages.
5 — A configurable content model or content types with reusable components, locales managed side by side for each entry, and an export of entries in JSON, CSV, XML or a similar documented format.
8 — References between entries, field-level localisation with fallback languages, variants per market or audience, translation workflows with status per locale and named translation-service connectors, and a full export of content, model, locales and assets documented and self-service.
10 — The repository is portable by design: model and content exportable together and re-importable, migration tooling or a CLI documented in both directions, version history included in the export, and no feature that only works while the content stays.
The Head of Content
There are 100+ templates, a content editor and collaboration in 30+ languages — though the captured pages give different figures for language support, 30+ and 20+ — which sits at the level of templates and multilingual content. We found no public information on a configurable content model, reusable components, locales managed side by side per entry, or a documented export format for the repository. 5 8
The SME Marketer
A template library of 100+ and broad language support are documented — the captured pages give different figures, 30+ in one place and 20+ in another, for the language claim. We found no public information on a configurable content model, locales managed side by side, or a documented export format, so a German master with an English variant is not described. 5 8
The Localisation Lead
AI generation across more than 30 languages, 100+ templates and an API that generates copy for any channel are documented, but we found no public information on a configurable content model, locales on the field with fallbacks, translation status per language, or a documented export of content, model and assets. This is a generator, not a localisation repository — whatever a team stores in the Brand Hub stays there on faith. 5 7 8
The Web Engineer
The product offers 100+ templates, a content editor, and generation in many languages, but the captured pages show no configurable content model, no reusable components with per-entry locales, and no documented export of entries in JSON, CSV or a similar format. The seven API domains are all generation-side — content, brand voice, images, audiences, twins — rather than a repository you own and can take with you. 5 6 7 8
The Data Protection Officer
Templates and multilingual output are evidenced — more than one hundred templates and a claim of thirty plus languages — and the API generates copy "for any channel" in the brand voice. We found no public information on a configurable content model, reusable components, locales managed side by side per entry, or a documented export of the whole repository in JSON or a similar format. Without an export path in the terms or the API documentation we read, I could not sign off on getting a customer's content back out. 5 6 8
The Skeptic
Content is generated per channel in a stored brand voice, and the Brand Hub holds voices, documents and audiences — but we found no public information on a configurable content model, reusable components, locales managed side by side for the same entry, or a documented export of the repository in any format. The API generates content; the pages do not document an export that would let content leave with model and history intact. 5 6 8
Publishing, distribution & integrations
Show reasoningHide reasoning
How this is scored
Getting approved content to where it is read: publishing to websites and channels, a documented API and webhooks, and named connections to the CMS, CRM, analytics, SEO and translation tools a marketing stack already runs.
0 — A closed tool; content leaves only by copy and paste.
3 — Publishing to one website or CMS, and a few named integrations.
5 — Publishing to websites and several channels from one place, a publicly documented API or webhooks, and integrations named for common CMS, CRM or analytics tools.
8 — A versioned API with published rate limits and SDKs, webhooks on publish and change, preview environments, a marketplace or integration directory with maintained connectors, performance data per piece pulled back from analytics, and a public status page.
10 — The platform is a dependable source for every channel: API deprecation policy published, CDN and delivery SLA stated, scheduled and event-driven publishing documented end to end, and content performance attributed per channel without a separate tool.
The Head of Content
This is the strongest area: 88 endpoints across 7 domains, a versioned API with a public changelog and published rate limits per plan, a hosted connector server for Claude Desktop, Cursor and Windsurf, a 99,9 % SLA from the Scale plan and a live status page. We found no public information on publishing to a named CMS or CRM, webhooks, SDKs, or per-piece performance data pulled back from analytics — so the route from approved draft into our website is not documented. 6 7
The SME Marketer
One key covering seven API domains and 88 endpoints, a versioned API with a public changelog, published rate limits (60 requests per minute on Developer, 600 on Scale, custom on Enterprise), OAuth 2.0 with PKCE, a hosted MCP server, a public status page and a 99.9% SLA from Scale are all documented. We found no public information on webhooks, on publishing into our CMS, or on named connectors for common CMS, CRM or analytics tools. 6 7
The Localisation Lead
One key, seven domains, 88 endpoints, a versioned API with a public changelog, published rate limits (60 requests per minute on Developer, 600 on Scale, custom on Enterprise), OAuth 2.0 with PKCE, a hosted MCP server and a public status page with a 99.9 percent SLA from Scale are all documented. We found no public information on webhooks, SDKs, preview environments or named connectors to the CMS, CRM and analytics tools a marketing stack already runs. 6 7
The Web Engineer
The strongest engineering story in the captures: a versioned API with a public changelog, 88 endpoints across 7 domains, rate limits published outright (60 requests/min on Developer, 600 on Scale, custom on Enterprise), OAuth 2.0 with PKCE plus self-serve bearer keys, a hosted MCP server for Claude Desktop, Cursor and Windsurf, a live status page and a 99.9% SLA from Scale. What holds it below the top level: we found no public information on webhooks on publish, SDKs, preview environments, or named connectors into the CMS, CRM and analytics tools a marketing stack already runs. 6 7
The Data Protection Officer
The API is public, versioned with a public changelog, and carries published rate limits — sixty requests per minute on Developer, six hundred on Scale, custom on Enterprise — plus a hosted MCP server for Claude Desktop, Cursor and Windsurf, OAuth 2.0 with PKCE, a status page and a 99.9 percent SLA from Scale. We found no public information on connectors to common CMS, CRM or analytics tools, webhooks, or SDKs. Seven API domains with eighty-eight endpoints make a serious integration surface, but the pages we read document generation and management endpoints rather than delivery into a customer's existing publishing stack. 6 7
The Skeptic
The API is publicly documented and versioned with a changelog, published rate limits (60 requests per minute on Developer, 600 on Scale), OAuth 2.0 with PKCE, 88 endpoints across 7 domains, a hosted MCP server for Claude Desktop, Cursor and Windsurf, a live status page and a 99.9% SLA from Scale. We found no public information on webhooks, SDKs or maintained connectors to the CMS, CRM and analytics tools a stack already runs, and "copy for any channel" describes generation, not publishing to those channels. 6 7
AI assistance & content rights
Show reasoningHide reasoning
How this is scored
What the platform's AI does with the customer's content and what the customer may do with the AI's: the models and where they run, whether content trains them, opt-out, labelling of generated text under the EU AI Act, and who holds the rights to output.
0 — The vendor states that customer content trains its models with no opt-out, or reserves the rights to AI output for itself.
3 — AI writing features described with what they do, and a general statement on how content is handled by them.
5 — The AI model provider named, a statement that customer content does not train models, and AI features that an admin can switch off.
8 — Model providers listed as subprocessors, EU processing for AI features stated or selectable, retention of prompts and outputs given in days, ownership of generated output assigned to the customer in the terms, generated content markable for EU AI Act transparency, and brand voice or terminology rules applied without training a shared model.
10 — AI is governed and documented: per-feature list of model, provider and processing location, admin controls per role and content type, an audit trail of AI-generated changes, and the output rights and any indemnity written into the contract terms.
The Head of Content
The models are named — GPT, Gemini, Claude, Mistral — and the pages state three times over that inputs, brand voice and stored documents never train public or shared models, with AI queries processed in the EU and the USA on Data Privacy Framework-certified providers. We found no public information on admin switch-off of AI features, retention periods for prompts and outputs, ownership of generated text in the terms, or marking for EU AI Act transparency. 3 5 6 7 8
The SME Marketer
The pages state repeatedly that inputs never train public models and that brand voice, guidelines and documents are not used for training AI models, name GPT, Gemini, Claude and Mistral as switchable models, and state that AI queries are processed in the EU and the USA on external providers under the EU-US Data Privacy Framework. We found no public information on who owns the generated output, an admin switch-off for AI features, retention of prompts, or EU AI Act labelling of generated text. 3 5 6 7 8
The Localisation Lead
Model providers are named (GPT, Gemini, Claude, Mistral), the pages state that inputs never train public models and that brand voice, guidelines and documents are not used for training, and AI query processing in the EU and the USA is disclosed with US providers certified under the EU-US Data Privacy Framework. We found no public information on an admin switch-off for AI features, retention periods for prompts and outputs, ownership of generated output in the terms, or labelling of generated content for EU AI Act transparency. 3 5 6 8
The Web Engineer
Model families are named (GPT, Gemini, Claude, Mistral), three separate captures state that inputs, brand voice and documents never train public models, and the privacy statement places AI queries in the EU and the USA with US providers under the EU-US Data Privacy Framework. We found no public information on an admin switch-off for AI features, retention of prompts and outputs in days, output ownership in the terms, or EU AI Act labelling of generated text. 3 5 6 7 8
The Data Protection Officer
The model families are named — GPT, Gemini, Claude, Mistral — and three captured pages state that inputs never train public models and that brand voice, guidelines and documents are not used for training, which is the direction I want. Those statements sit on product and API pages, however; we found no public information on training exclusion written into the terms, on prompt or output retention in days, on ownership of generated output assigned to the customer, or on marking generated content for EU AI Act transparency. AI queries are processed "in the EU and in the USA on servers of external providers", with the US providers identified only by their Data Privacy Framework certification — for sign-off I need them named as subprocessors with their role. 3 5 6 7
The Skeptic
The models are named — GPT, Gemini, Claude and Mistral — three captured pages state that inputs, brand voice, guidelines and documents are not used to train models, and the privacy statement discloses that AI queries run in the EU and in the USA on external providers certified under the EU-US Data Privacy Framework. We found no public information on retention periods for prompts and outputs, who owns the generated output, EU AI Act labelling, or an admin switch to turn AI features off per role or content type. 3 5 6 7 8
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity is, where content, assets and AI prompts are stored and processed, and which subprocessors touch them. Independently sourced by the sovereignty pipeline; dimensions the evidence does not establish are unknown, not non-European.
0 — Vendor, contracting entity and hosting all shown to be outside the EU, with no data processing agreement offered.
3 — A privacy policy and a data processing agreement offered, with hosting or the contracting entity outside the EU or not established.
5 — EU hosting stated for content and assets, with a data processing agreement offered.
8 — EU contracting entity, content, assets and backups stored in the EU on named infrastructure, subprocessor list published with locations and purposes, and AI processing location stated.
10 — Sovereign end to end and evidenced: European ownership, EU entity, every hosting, CDN, AI and support subprocessor European or optional, self-hosting or a European cloud offered, and certifications published.
The Head of Content
The vendor's own pages establish a German contracting entity (neuroflash GmbH, Hamburg, registered at Amtsgericht Hamburg), personal data stored in the EU on Google Cloud Platform and at Raidboxes in Germany, ISO 27001 certification, and named subprocessors with country, purpose and transfer basis (Stripe and Stape in the USA, Usercentrics in Munich). AI queries run in the EU and in the USA, and the independently collected sovereignty data marks ownership, the data processing agreement, hosting options and open source as unknown, so this stays mid-band rather than sovereign end to end. 2 3 5 7
The SME Marketer
The contracting entity is neuroflash GmbH of Hamburg (Amtsgericht Hamburg, HRB 117450) with a named data protection officer in Hamburg, hosting is stated on EU servers — Google Cloud Platform and Raidboxes in Germany — under ISO 27001, and subprocessors are published with country and purpose (Usercentrics in Germany, Stape and Stripe in the USA). AI queries are additionally processed in the USA under the Data Privacy Framework, and we found no public information on a data processing agreement or backup locations. 2 3 5 7
The Localisation Lead
The contracting entity is neuroflash GmbH of Hamburg with a German register court and VAT number, personal data is stored in the EU on named infrastructure (Google Cloud Platform and Raidboxes in Germany), ISO 27001 is claimed, and subprocessors are published with country and purpose — Stripe and Stape in the USA under SCC or Data Privacy Framework cover, Usercentrics in Munich. AI queries are processed in the EU and the USA on external providers, and we found no public information on backup locations or European ownership of the vendor. 2 3 7
The Web Engineer
neuroflash GmbH is a Hamburg-registered company with a named data protection officer, personal data is processed in the EU on named infrastructure — Google Cloud Platform and Raidboxes in Germany, ISO 27001 certified — and subprocessors are listed with country, purpose and transfer basis (Stripe and Stape in the USA, Usercentrics in Munich). AI processing location is stated as EU and USA, and we found no public information on self-hosting or a European cloud option, which caps it below the top level. 2 3 7
The Data Protection Officer
The contracting side is solid: neuroflash GmbH, registered at Amtsgericht Hamburg under HRB 117450 with a Hamburg address, a named external data protection officer in Hamburg, and ISO 27001 certification. Servers are stated to be in Germany and the EU on named infrastructure — Google Cloud Platform and Raidboxes — with consent-based cookies under Art. 6 GDPR and standard contractual clauses as the fallback for US providers. The deductions are the AI path and the paperwork: AI queries also run in the USA on external providers who are not individually named, the processor disclosures we read cover payment (Stripe), server-side tracking (Stape) and consent (Usercentrics) rather than the model providers, and we found no public information on a data processing agreement or a European option for the US processing. 2 3 7
The Skeptic
The contracting entity is neuroflash GmbH of Hamburg with a German register number and a Hamburg data protection officer, hosting is stated on Google Cloud Platform and at Raidboxes in Germany under ISO 27001, and the privacy statement publishes subprocessors with location and purpose, including the US processors Stripe and Stape under standard contractual clauses. AI queries are processed in the EU and in the USA rather than EU-only, and we found no public information on a data processing agreement or where backups sit. 2 3 7
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the annual cost for their team, locales and traffic from public pages alone — seats and contributor roles, locales, content records, API calls and bandwidth, AI credits, and the plan where approval workflows or SSO begin.
0 — No public prices at all; every plan is a sales conversation.
3 — A public "from" price, a free tier, or one priced plan, with the rest on request.
5 — Prices for each plan public with the billing period (per month or per year) and the seats or main limits each includes.
8 — Every plan priced with seats, locales, records, API and bandwidth limits and overage rates stated, AI usage priced or included explicitly, and the plan that unlocks approval workflows, SSO and audit logs named.
10 — Complete cost computability: annual cost derivable for a given team, locale count and traffic, every add-on and overage priced publicly, contract term and renewal conditions stated, and the cost of exporting or leaving the platform zero or published.
The Head of Content
A free tier with 5.000 Credits per day, pay-as-you-go ab 0,20 € pro 1.000 Credits, published credit costs per deliverable (a blog article 20 CU, a social media post 5 CU) and published rate limits per plan let a team sketch what the AI will cost. We found no public information on a price for the Scale plan, seat-based pricing for teams, or which plan unlocks approval workflows, SSO and audit logs, so the annual cost of a real editorial team is not computable from these pages. 5 6 7
The SME Marketer
Public and quotable are a free tier ("Start for free", 5,000 free credits per day, self-serve), pay-as-you-go at "Ab 0,20 € pro 1.000 Credits", per-output credit costs (blog article 20 CU, twin query 6 CU, AI image 6 CU, social media post 5 CU) and per-plan rate limits. The seat-based team plans carry no published prices — Enterprise is "Individuelles Angebot" — and we found no public information on guest seats, per-locale costs or billing periods, so an annual cost for a second language plus agency guests cannot be computed from these pages. 6 7 9
The Localisation Lead
A free Developer tier (5,000 credits per day, 60 requests per minute), pay-as-you-go at ab 0,20 € pro 1.000 Credits and per-output credit prices (blog article 20 CU, social media post 5 CU, AI image 6 CU, twin query 6 CU) are public, which makes AI generation costs genuinely computable. Enterprise is an individual quote, the captured pages give no public seat prices for the team plans, and we found no public information naming the plan that unlocks SSO or approval workflows. 6 7
The Web Engineer
Usage pricing is unusually concrete: a free Developer tier with 5,000 credits per day and 60 requests/min, pay-as-you-go at 0,20 € per 1.000 Credits, published credit costs per artefact (blog article 20 credits, AI image 6, social media post 5), and Enterprise as an individual quote. But the captured pages give no price for the Scale subscription plan, no seats or contributor-role pricing, and no statement of which plan unlocks approval workflows, SSO or audit logs, so an annual team cost is not computable from public pages alone. 6 7 8
The Data Protection Officer
Public pricing exists and is concrete on usage: a free start, a Developer tier at zero euro with five thousand credits per day, pay-as-you-go "ab 0,20 € pro 1.000 Credits", and per-output credit costs — twenty credits for a blog article, six for an image or a twin query, five for a social media post. Enterprise is an individual quote, and a Scale plan appears in the rate-limit and SLA tables without a price on the pages we read; we found no public information on seat-based team pricing or on which plan unlocks approval workflows or SSO. A time-limited promotion of "up to 25% off until Cyber Monday" further changes the number a buyer would pay today. 6 7
The Skeptic
A free tier with 5,000 credits per day, pay-as-you-go "ab 0,20 € pro 1.000 Credits", published per-output credit costs (a blog article at 20 CU, an image at 6 CU, a social post at 5 CU) and public rate limits let a buyer price generation usage before any sales call. But the Enterprise plan is an individual quotation, we found no public prices for the subscription plans with seats and billing period, and no public information on overage rates beyond the credit price or on which plan unlocks team and approval features. 6 7 8
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Neuroflash
Is Neuroflash European?
Not determined: the vendor’s pages as captured do not say where Neuroflash is based.
Where does Neuroflash store data?
The default storage location for customer data is not stated on the vendor’s pages as of 17 Nov 2026. The vendor’s pages mention Germany as hosting location, per the vendor’s page captured 17 Nov 2026.
Does Neuroflash have a free plan?
Yes. Neuroflash has a free plan, per the vendor’s page captured 17 Nov 2026.
What are the best alternatives to Neuroflash?
As of 19 Nov 2026, the panel rates Kontent.ai (3.5/5), StoryChief (3.5/5) and Scompler (3/5) highest among the other 30 Content Marketing products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Kontent.ai (EU-Made, Czechia). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Neuroflash alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 17 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 9 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 subprocessors fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (9)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page neuroflash.com Checked 17 Nov 2026 Details →
- 2 Legal notice — found from the homepage neuroflash.com Checked 17 Nov 2026 Details →
- 3 Privacy policy — found from the homepage neuroflash.com Checked 17 Nov 2026 Details →
- 4 Creation, review & approval — found from sitemap neuroflash.com Checked 17 Nov 2026 Details →
- 5 Creation, review & approval — found from sitemap neuroflash.com Checked 17 Nov 2026 Details →
- 6 Publishing, distribution & integrations — found from sitemap neuroflash.com Checked 17 Nov 2026 Details →
- 7 Publishing, distribution & integrations — found from sitemap neuroflash.com Checked 17 Nov 2026 Details →
- 8 AI assistance & content rights — found from sitemap neuroflash.com Checked 17 Nov 2026 Details →
- 9 AI assistance & content rights — found from sitemap neuroflash.com Checked 17 Nov 2026 Details →