For AI-native people
Your website task. A process you can inspect.
Berlzop uses an agent harness: the execution layer around an AI model that connects project context, permitted tools and work steps. Its purpose is website work with previews and approval. Here is what has been checked and where the new customer path still has limits.
Discuss my website taskAn AI service for your website. Your first preview is free, with no commitment. €99 a month from publication, cancel monthly. No setup fee. No separate AI subscription needed.
Current status: The bot and sign-in to your own account are available. New paid website orders and automatic handling of new support enquiries remain closed. You can already discuss your project with us by email without committing to an order.
What works behind the conversation
Execution and toolsChecked in staging
The core executes bounded tasks with files, a terminal and a browser. Website previews have a separate approval step. The tools your access includes must be agreed before starting; outside files and websites cannot grant permissions.
Models and usageOpen before customer launch
The technical core includes Claude and Codex adapters. This does not authorise processing personal support data through them: that processing is blocked until a provider with a data processing agreement and safeguards for third-country transfers is connected. The website package does not require your own AI subscription. A specific model or unlimited use is not promised.
Context and project filesChecked in staging
Project files and saved agreements can persist between sessions. Model context is limited; information is loaded selectively or summarised. This is not complete or infallible memory.
Data and boundariesOpen before customer launch
The core separates customer workspaces. Received support cases stay on our server and can be answered manually; they are currently not sent automatically to an AI model. The public AI information chat is a separate service with its own privacy notice. Complete export, retention and recovery of customer operations still need operational review. A German server does not mean all processing stays in Germany.
Results you can inspectChecked in staging
Draft, check result, approval and published state are separate steps. A finished agent run does not count as a published website. Costs and external effects need their own receipts; uncertain actions are reconciled before retrying.
Failures and operational launchOpen before customer launch
The core includes failure records and repair checks. A fully evidenced, independently running Berlzop customer operation is still outstanding. Shops, arbitrary integrations and autonomous purchases are not automatically part of your website task.
An actual example of the work
A design you can actually see.
Baumlandgarten: a website, copy and leaflet with a consistent design. This existing example shows design work. It does not prove the new automated customer journey or any particular business result.
The technical status labels refer to isolated core checks. A first real customer purchase and a subsequently completed task require separate evidence.
What the package includes
Creation, hosting, one domain, one mailbox and ongoing updates to copy, images and pages are included. Before starting, we discuss content, design and the right scope. Shops, bookings or user accounts need a separate scope agreement. Your first preview stays free and non-binding.