# Kamu.build docs > How to build, edit and run websites on Kamu.build, by hand or with your own AI agent. # Welcome to the Kamu.build docs Kamu.build is a website platform built for agents. Your site is a real static website with hosting, certificates, forms, analytics and domains taken care of. You can build and edit it with your own AI agent, with Kamu (the built-in agent), or by hand in the dashboard. ## How does it work? There are two ways in. ### 1. Connect your own AI agent Connect Claude, ChatGPT, Claude Code or another MCP client to `https://mcp.kamu.build`. 1. **Connect**: add the address as a connector in your agent and log in. If you have no account yet, you create one while connecting 2. **Create a site**: the agent creates a trial site for your team. It gets a free 30-day trial and an address of its own 3. **Write and publish**: the agent writes the content and publishes it, if you gave it the permission to publish 4. **Take it into use**: the agent can start an order for a plan and a domain. You confirm and pay the order yourself; the agent never buys anything The steps for each app are in [Connecting an app](/mcp/connecting). What the agent can and cannot do is in [Your own AI agent (MCP)](/mcp/overview). ### 2. Create the site in the dashboard 1. **Sign up or log in** at [app.kamu.build](https://app.kamu.build) 2. **Create a site**: click **Create site** on the **Sites** page, choose the site type and describe what you want to build. If you already have a website, Kamu can use it as the basis 3. **Check the details** and start the build. Kamu, the built-in agent, builds the site. It usually takes about half an hour, and you can follow it in the dashboard 4. **Review and edit**: make changes with Kamu in Studio, ask the Assistant for them, or edit texts yourself in the dashboard. You can also connect your own agent to the site later 5. **Take the site into use**: choose a plan and a domain, or continue first with the free 30-day trial The steps are in [Your first website](/getting-started/first-site). ## All guides ### Getting started - [Signing up](/getting-started/sign-up): creating an account and logging in - [Your first website](/getting-started/first-site): how to start your first website - [Dashboard](/getting-started/dashboard): how to use the dashboard ### Your own AI agent (MCP) - [Overview](/mcp/overview): what your own agent can access and do - [Connecting an app](/mcp/connecting): Claude, ChatGPT and Claude Code - [Documents with your own app](/mcp/documents): creating and editing the team's documents ### Managing your site - [Site structure](/site/structure): site structure and contact details - [Site terminology](/site/glossary): a glossary of page parts for precise requests - [Visitor analytics](/site/analytics): cookie-free visitor statistics - [Google Analytics](/site/google-analytics): Google Analytics and the cookie banner - [Google Business Profile](/site/google-business-profile): your business in Google Search and Maps - [AI permissions](/site/ai-crawlers): what AI systems and search engines may do with your content - [Notifications](/site/notifications): email, push, and WhatsApp notifications - [Images and media](/site/images-and-media): adding and managing images - [Blog](/site/blog): publishing blog posts - [Integrations](/site/integrations): forwarding form submissions to your own systems - [Site migration](/site/migration): getting source code and migrating away ### Editing your site - [AI assistant](/editing/ai-assistant): how the AI assistant works and what it can do - [Chat](/editing/chat): edit your site in the dashboard chat view - [Studio](/editing/studio): real-time editing view with a live preview - [WhatsApp](/editing/whatsapp): edit your site via WhatsApp - [Blog posts](/editing/blog-posts): creating and editing blog posts - [Text editing](/editing/texts): editing texts directly - [Publishing](/editing/publishing): automatic and manual publishing ### Third-party services - [Appointment booking](/services/booking): linking your own booking system to the site - [Newsletter](/services/newsletter): a newsletter service's signup form on the site - [Comments](/services/comments): comments on blog posts ### Domains - [Domain management](/domains/your-domain): registration and management - [Domain transfer](/domains/transfer): transferring from another provider - [Connecting to a site](/domains/connecting): linking a domain to your site - [DNS settings](/domains/dns-settings): technical DNS configuration guide - [Email](/domains/email): email forwarding and sending with your own domain - [BIMI logo](/domains/bimi-logo): your company logo in the recipient's inbox ### Billing - [Plans](/billing/plans): plan options and pricing - [Invoices](/billing/invoices): viewing and paying invoices - [Agent credit](/billing/agent-credit): the credit for site updates, Studio and documents; top-ups and consumption ### Other - [Documents](/documents): presentations, documents, and diagrams with Kamu - [Shop](/shop): products, orders and shop settings - [FAQ](/faq): answers to common questions - [Changelog](/changelog): customer-visible changes to the service --- # Documents On the **Documents** tab you make more than websites with Kamu: documents, presentations and single-page publications such as invitations, menus and announcements. You'll find it in the dashboard top bar. The feature is still in beta. You can also create and edit documents with your own AI app, see [Documents with your own app](/mcp/documents). Documents are edited in the Studio editor, so editing them uses [agent credit](/billing/agent-credit) the same way as editing your site in Studio. If your balance has run out, you cannot open a document until you top up. ## Document types - **Document**: an A4 document you can print to PDF and send for signature, for example a contract, an offer or a letter - **Presentation**: a slide deck you can publish as a link - **Page**: a single page with a free-form layout. You can start from a blank page or a ready template: ad, invitation, menu, announcement, certificate, form or diagram - **Brand book**: your company's colours, fonts and logo in one place, so other documents can use them Printable documents, diagrams, forms and HTML pages created earlier are shown in the list and open in the editor as before. ## Team The Documents page shows one team's documents at a time. If you belong to several teams, switch the team with the **Team** picker in the top right corner of the page. The same team is selected on the other dashboard pages too, such as Billing. ## Creating a document 1. Choose the document type under **New**: **Document**, **Presentation** or **Page**. 2. Give the document a name. 3. If the team has a brand book, it is already selected under **Brand**. The document then uses your company's colours, fonts and logo. Choose **No brand** if you don't want to use the brand book. 4. For a page you also choose a **Template**: blank page, diagram, form, ad, invitation, menu, certificate or announcement. 5. Press **Create and open**. The document opens for editing in the Studio editor, and you can tell Kamu right away what content you want. The arrow in the editor's top left corner takes you back to the document list. ## Brand books Brand books are shown on their own row above the document list. A card shows the brand's colours and fonts. You make a new brand book from the **New brand book** card. In the new brand book dialog you can copy the brand from an existing website. Type the site's address under **Copy from website**, for example example.com, and press **Read**. The logo, colours and fonts are fetched from the site, and you can change them before you create the brand book. If no logo is found, the brand book gets a placeholder you can replace with your own logo. Only openly licensed fonts can go into a brand book. If the site's font is not one, another font is suggested in its place. Reading a site requires some agent credit to be left. ## Editing a document A document opens in the Studio editor. On the left you chat with Kamu, on the right you see the document. Working with Kamu is the same as in [Studio](/editing/studio): attachments, dictation, the queue and **Pick what to edit** work the same way. - **Edit / View**: for the Document type, **Edit** opens the document for editing like in a word processor. Select a text to bring up the formatting tools and the **Ask Kamu** button, with which you can ask Kamu to change exactly that part. **View** shows the document as it prints, and its PDF button shows the printed pages. In presentations and pages, **Edit** mode lets you change texts directly in the preview. - **Save**: saves Kamu's changes and your own to the document with one click. A dot on the button tells you there are unsaved changes. - **Discard**: takes the document back to how it was last saved. Every change made since then, yours and Kamu's, is removed. The same action is also in the version menu. - **Publish to web**: publishes the document at its own address. Choose whether the page is **Public** or **Password protected**. The button is shown until the document has been published. With the menu next to the **Version** picker in the top bar you can make a new version of a document or rename a version the same way as in a site. A new version gets its name from your first request or save. ## Signature requests A document of the Document type can be sent for signature. The signature is a simple electronic signature. Documents made in the older format cannot be signed, and the menu is not shown for them. 1. Open the editor's **Signatures** menu and choose **Add signature block**. Kamu adds a signature block at the end of the document. Every signer needs a slot of their own in the block, and you add more slots with **Add a signature slot**. 2. Choose **Request signatures** from the same menu. The document is saved and turned into a PDF. The signers get exactly this PDF. 3. Give a signer's name and email address for each signature slot. The requests go out to everyone at once, so every slot needs a signer. If there are too few slots, ask Kamu to add one. You can also write a message. 4. Press **Send requests**. The signers get an email with a link to the signing page, with the PDF attached. The links are also shown in the dialog, if you want to share them yourself. The requests you send make up a signing round. You can keep editing and saving the document. Your changes do not affect the PDF out for signing, since the signers sign the PDF that was sent to them. To have a changed document signed, cancel the waiting round and send a new one. A document can have one round waiting for signatures at a time. You can send a new round once the previous one has been signed or cancelled. On the signing page the signer sees the same PDF, types their name and town, draws or types the signature, and confirms it with a 6-digit code sent to their email. A signer can also decline to sign, which ends the round. The document is signed only once every signature slot has been signed. Then every party gets the signed PDF by email, with the signing details at the end. While a round is waiting for signatures, a note about it is shown at the top of the editor, and the **Signatures** menu shows how many have signed, for example **Waiting for signatures 1/2**. It opens the round's dialog, with the same actions as in the document list, see [Signing rounds](#signing-rounds). ## Folders The top folder of the document list is **Home**. You make a new folder above the list with **New folder**. You can make a folder inside a folder with a slash, for example Contracts/2026. - Move a document into a folder by dragging its row onto the folder. In the same way you move a folder into another folder or back to Home. - With the **+** button on a folder row you can make a document or a folder straight into that folder. - You can rename a folder with the pencil button. Its documents stay in the folder. - An empty folder can be removed with the bin button. You can sort the list by name, type or modification time from the column headers. Folders and documents are sorted together. The search field and the type picker help you find a document quickly. Clicking a document's name opens it in the editor. With the pencil button on the row you can rename a document and with the bin button remove it. A published document's address does not change even if you rename it. ## Who sees a document The **Visibility** column tells who in the team sees the document: - **Team**: all team members see the document and can edit it. New documents are visible to the whole team by default. - **Private**: only the document's creator sees it. Clicking the label switches the visibility. ## Signing rounds Every signing round is shown in the document list as a row of its own under its document, newest first. The row is named by the day it was sent, and a label shows the round's status: - **Waiting for signatures 1/2**: the requests have been sent, and the label shows how many have signed. - **Signed**: everyone has signed. - **Cancelled**: the round has been cancelled. - **Declined**: one of the signers declined to sign. Clicking the row opens a dialog with the round's PDF and the signers and their status. Once everyone has signed, the dialog shows the signed PDF. In a waiting round you can manage the signers who have not signed yet: - **Send link again** sends the signer a new link if the email got lost. The earlier link stops working. A link can be sent again only a few minutes after the previous send. - **Replace signer** sends the request for the same slot to another person. The earlier signer's link stops working, and they are told about it. - **Download PDF** downloads the round's PDF, and once everyone has signed, the signed PDF. - **Cancel round** cancels the whole round, also when someone has already signed. All links stop working, and those who already signed are told by email that the round was cancelled. A cancellation cannot be undone. You can also download the PDF or cancel a waiting round straight from the row's buttons. A round cancelled before anyone signed disappears from the list. ## Publishing When you publish a document on the web from the editor, it gets a public address you can share, for example with a customer. The **Online** column then shows **Public**, or **Protected** for a password-protected page, and the label opens the page. A published document's row has a lock button with which you can set a password for the page. Removing a document from the list does not take a published page offline. --- # Web shop The **Web shop** tab lets you sell products on your own site. The feature is in beta and is enabled per team. If you would like to try it, ask for it through the assistant behind the dashboard's **?** button or at [kamu.build/contact](https://kamu.build/contact). Once the shop is enabled, the tab appears in the dashboard's top bar. :::note[Currently for companies in Finland] The shop is built for Finnish merchants for now: online payments are set up as a Finnish Stripe account, the invoice details ask for a Finnish business ID, and the shipping integration (Shipit) covers Finnish carriers. Prices are in euros. The shop pages of the dashboard are also in Finnish only, so the labels below are given in Finnish with a translation. ::: The team's owner and admins can change the shop's settings, products and orders. Members can see the information but cannot change it. ## Payment methods Payment methods are set on the **Maksutavat** (payment methods) tab. If more than one method is on, the customer picks one at checkout. At least one method has to be on. - **Online payments via Stripe**: customers pay at checkout through Stripe, and Stripe pays the sales out to your company's bank account after its fees. Setting it up: accept the payment terms, fill in your company's details in Stripe (business ID, responsible person and bank account, about 10 minutes) and wait for Stripe to check them. The status updates on the tab by itself. You choose in your own Stripe account which methods show at checkout, for example cards, bank payments, MobilePay, Apple Pay or Klarna. Refunds and payouts are handled in Stripe. The tab shows the costs: Stripe's own fees by payment method, plus a platform service fee on orders paid through Stripe. - **Lasku** (invoice): the customer pays by bank transfer with the invoice details and a reference number. The products are reserved for the customer until the due date. Fill in the seller name, business ID, address, VAT ID (if registered) and payment term. You choose whether the invoice goes to the customer automatically with the order confirmation or you send it yourself. There is no platform fee on invoice orders. - **Muut maksutavat** (other methods): if you need another method, such as Paytrail, you can send a request from this card. Opening the shop and selling by invoice are free. ## Creating a shop and adding it to your site 1. Press **Luo verkkokauppa** (create web shop) and give the shop a name. Only you see the name. 2. On the shop's **Yleiskatsaus** (overview) tab, pick a site and press **Linkitä sivustoon** (link to site). Linking connects the shop to the site but does not change the site's layout yet. 3. Under **Lisää kauppa sivustolle** (add the shop to your site), describe where you want the shop, for example as its own page in the menu or as featured products on the front page. Press **Käynnistä kaupan lisäys** (start adding the shop). Kamu adds the shop pages to your site in keeping with its current design, and you can follow the progress on the site's own page like any other update. It is an ordinary site update, and the same terms apply as to other updates. If you remove the link, the shop pages stay on the site, but they show no products until the shop is linked again. ## Tabs - **Yleiskatsaus** (overview): the number of products for sale and orders awaiting delivery, and the linked site. - **Tuotteet** (products): adding and editing products. The price includes VAT. The product code is optional: if you leave it empty, it is made from the product name. The code cannot be changed afterwards. You can upload images for a product (jpeg, png, webp or gif, up to 5 MB). Only products with the status **Myynnissä** (for sale) appear in the shop. **Saldo** (stock) is the quantity in storage, and **Vapaana** (available) is what is not currently reserved in customers' shopping carts. - **Tilaukset** (orders): orders by status (awaiting payment, paid, shipped, refunded, cancelled). For an invoice order, press **Merkitse maksetuksi** (mark as paid) when the bank transfer shows up in your account, so the products are not released back for sale. When the parcel has left, press **Merkitse lähetetyksi** (mark as shipped). The **Lasku** (invoice) button opens the order's invoice. - **Alennuskoodit** (discount codes): codes the customer enters at checkout. A discount can be a percentage or a fixed amount, and it can have a minimum order, a maximum number of uses and a validity period. The discount is calculated from the product total before shipping. - **Tilastot** (statistics): net sales, paid orders, average order, refunds and top products for the selected period. - **Maksutavat** (payment methods): see [Payment methods](#payment-methods). - **Toimitus** (shipping): **Toimitustavat** (shipping methods) and **Kiinteä toimituskulu** (flat shipping fee). - **Asetukset** (settings): the shop's notifications and their email recipients. ## Shipping Shipping methods (for example pickup point, home delivery or in-store pickup) get a name and a price, and you can set a limit above which an order ships free. The customer picks one shipping method at checkout. If no shipping methods have been added, the flat shipping fee is added to the order. If the shop has a Shipit account, connect its key on the **Toimitus** tab. **Hae toimitustavat Shipitistä** (fetch shipping methods from Shipit) then lists the account's services: the common ones (Posti and Matkahuolto parcel and pickup-point services) first, the rest in a list you can expand. The ones you pick are added as shipping methods, switched off, priced at what Shipit charges for a 1 kg parcel rounded up to 10 cents. Check the price and switch each on, and it appears at checkout. For pickup-point deliveries the customer chooses a pickup point at checkout by postcode. The shipping method's price is what the customer pays. To make it follow weight, add weight tiers to the method (for example up to 1 kg 8.30 €, up to 5 kg 8.30 €, up to 10 kg 11.70 €): the checkout picks the tier by the order's weight, and an order heavier than the last tier pays the last tier's price. Product weights are set in the product details. The method editor shows what Shipit charges your account for 1, 5 and 10 kg parcels, and **Käytä Shipit-hintoja** (use Shipit prices) copies them in as the price and tiers. Shipit's prices are fetched once a day and on demand with **Päivitä hinnat Shipitistä** (refresh prices from Shipit); a refresh never changes your methods' prices. A method can also carry a delivery time (for example "1–3 business days"), shown to the customer at checkout. ## Notifications The shop's notifications, for example new orders, appear in the dashboard's bell. In the **Ilmoitukset** (notifications) section of the **Asetukset** (settings) tab you choose which addresses also get them by email, and for which events. A new shop has the email address of the user who created it as its default recipient. Without a recipient the shop sends no notification emails, not even for new orders, so check the addresses if someone else handles the orders. ## Assistant The dashboard assistant can list the shop's products and orders. It can also propose new products or changes to prices, stock and descriptions, and mark an order as paid or shipped. The assistant saves nothing by itself: the proposal appears in a card that you save or cancel. --- # Changelog The kamu.build docs started on 16.11.2026. The list goes back to v1.102.0; earlier changes to the platform are not listed here. ## v1.115.0 (16.11.2026) ### Changes - Sending a document for signature no longer locks it. You can keep editing right after sending, without making an editable copy. Signers see the PDF as it was when sent; edits do not change it. - A signature request goes to every signature slot of the document at once. Each slot needs a name and an email address before sending. - In the Documents list, each signing round is its own row under the document, with its status (waiting, signed, cancelled, declined). The row opens the PDF and the signers: send a link again, replace a signer or cancel the round. Read more: [Documents](/documents) - A document can have one waiting signing round at a time. ### Fixes - A document is no longer marked signed when the request went to only some of its signature slots and they signed. ## v1.114.3 (14.11.2026) ### Fixes - The Publish button in Studio's toolbar stays visible in a narrower window. When space runs out, secondary buttons show only their icon, and their name appears on hover. - Pressing Publish again on a version that is already published no longer ends in an error. ## v1.114.2 (14.11.2026) ### Fixes - A domain connected to a site no longer stays **Awaiting verification** once its DNS records point correctly. Read more: [Connecting to a site](/domains/connecting) ## v1.114.1 (14.11.2026) ### Fixes - When a domain's DNS records are changed to point at the site, its status no longer keeps showing the old records for about an hour. **Check status** also sees the change right away. Read more: [Connecting to a site](/domains/connecting) ## v1.114.0 (13.11.2026) ### New - You can connect your own AI agent without an existing account: choose Create account on the sign-in page and give your team a name. Read more: [Connecting an app](/mcp/connecting) - An agent connected to the whole team at the edit level can create a new trial site and build its content itself. Read more: [Creating a new site](/mcp/overview#creating-a-new-site) - An agent can draft an order for a site's plan and domain, which you confirm and pay yourself, and link a team domain to a published site. Read more: [Ordering a plan and a domain](/mcp/overview#ordering-a-plan-and-a-domain) - If a site's build fails after a publish, the site's people get a notification. It can be muted like other notifications. - Publishes from Studio and from agents show in the team's activity and the site's deployment history. ### Changes - When an order has a plan and one domain, the domain is linked to the site automatically after payment and registration. - A document's letterhead title can be set separately from the document's name. - Contact notifications also show checkbox, number and list answers. ## v1.113.0 (12.11.2026) ### New - An AI agent connected to a whole team can be given extra permissions: reading contact requests, reading invoices and billing details, and starting a domain purchase. The agent pays nothing: it makes a draft order that you confirm and pay yourself. Read more: [Your own AI agent (MCP)](/mcp/overview) - Under Connected apps in your profile, each agent's recent actions are listed, and a site's History page shows the changes agents have made. Besides changes, reading contact requests, invoices and document contents is recorded. ### Changes - Connected apps are shown as cards instead of a table on phones. ### Fixes - A document's password now applies also when it is set before the first publish. Before, the link opened without the password. ## v1.112.0 (12.11.2026) ### New - You can connect your own AI agent to a whole team: it then reaches all the team's sites, including ones added later, and its documents. Alternatively you can grant access to chosen sites only. Read more: [Your own AI agent (MCP)](/mcp/overview) - The agent can set a password on a document's public link when publishing, or remove it. ### Changes - The connection page is reworked. You choose one permission level (read, edit, or edit and publish), and above the buttons it shows what you are about to grant. ## v1.111.0 (12.11.2026) ### New - Your own AI agent can also create and edit your team's documents, for example write a new contract or offer. At login you choose the teams and permissions for documents separately. Read more: [Documents with your own app](/mcp/documents) - Your own AI agent (MCP) has its own section in the docs, with instructions for connecting Claude, ChatGPT and Claude Code. ### Fixes - Connecting Claude Code works. The login used to stop at the last step. - If the AI agent does not ask for permissions itself, the login page offers all of them to choose from. ## v1.110.0 (11 Nov 2026) ### New - You can edit your site with your own AI agent, for example Claude or ChatGPT. The agent connects to mcp.kamu.build, and at login you choose whether it may read, edit or also publish. This also suits an agency you have invited to the site. Read more: [Your own AI agent (MCP)](/mcp/overview) - In WhatsApp your message is marked as read and you see the typing indicator as soon as Kamu starts working on it. - The editor on the Posts page shows the cover image under the image field. ### Changes - If the site's file has changed since you started editing a post, the editor says so above the text. You can view the differences and choose whether to use the site's version or keep your own draft. - Several messages sent in a row are handled in the order they were sent, both in WhatsApp and in the dashboard chats. ### Fixes - The dashboard chat continues when the page is reloaded in the middle of an answer. The answer no longer goes missing. - Changes made to a site proposal (description, style, colours, logo) are saved and show when the proposal link is opened on another device. ## v1.109.0 (11 Nov 2026) ### New - A blog post can be written and updated in WhatsApp. Kamu saves the text as a draft, and it is published with the publish button in the message. Read more: [WhatsApp](/editing/whatsapp) - Kamu can read a web page whose link you send in the conversation and use it, for example, as a source for a blog post. ### Changes - When you give Kamu your own text for a blog post, it is saved as a draft straight away, without questions in between. ### Fixes - On phones and tablets the keyboard's Enter adds a new line in the chat field instead of sending the message. The message is sent with the send button. ## v1.108.2 (10 Nov 2026) ### New - A site draft can be discarded and started over from the published version. The discarded draft is kept and can be restored. Read more: [Studio](/editing/studio) - Versions are named automatically from the first request, and the name can be changed from the version menu. ### Fixes - Studio's preview now shows sites built with the older Tailwind version correctly, with their styles. - In split view the phone is shown at phone height and the desktop view at full height. ## v1.108.1 (10 Nov 2026) ### New - The status of signature requests is available at any time from the editor's Signatures button. There you can send a link again, cancel a request, add a signer in place of a cancelled one and download the signed PDF. Read more: [Signature requests](/documents#signature-requests) ### Fixes - The document list shows Signed only once everyone has signed. Before that it shows how many have signed so far. ## v1.108.0 (10 Nov 2026) ### New - Studio has been redesigned. You edit the site by chatting with Kamu, and the preview updates as changes are made. Text can be edited directly in the preview, and the Pick what to edit tool lets you point at the part you want changed. Save stores your changes in a draft, and Publish puts them on the site. - If the previous editor had unpublished changes, they appear in the new Studio as an unpublished draft. - On the Documents page you can create documents, presentations and pages with Kamu, organise them into folders and choose whether the whole team can see them. Read more: [Documents](/documents) - A brand book can be created from an existing website: the logo, colours and fonts are taken from the site. - A document can be sent for signature. The signer gets a link, sees the document as a PDF and confirms the signature with a code sent by email. The finished PDF with its certificate is sent to every party. ### Fixes - Refreshing the Domain page now also reloads the status of operations and the registry. ## v1.107.0 (7 Nov 2026) ### New - When rebuilding a site you can pick a style for it, such as Quiet, Bento or Nordic. By default the builder picks a style that fits the business. ## v1.106.0 (6 Nov 2026) ### New - Contact form submissions are checked for spam. Suspicious messages go to the Spam section of the Contacts page, from where a genuine message can be delivered. Read more: [Notifications](/site/notifications#spam) ## v1.103.0 (5 Nov 2026) ### New - The shop notifies you by email and in the notification bell when Stripe starts accepting card payments for the shop. The notification can be switched off in the shop's notification settings. ## v1.102.0 (5 Nov 2026) ### New - Shop shipping methods can have weight tiers, so the shipping fee follows the order's weight, and a delivery time shown to the customer at checkout. See [Shop](/shop#shipping). ### Changes - The Stripe setup for card payments opens in a new tab, and the dashboard updates its status when you return. --- # Frequently Asked Questions (FAQ) ## General ### What is Kamu.build? Kamu.build is a website platform built for AI agents. You connect your own agent, such as Claude or ChatGPT, or let Kamu, the built-in agent, build the site from your description. Hosting, certificates, forms, analytics and domains are taken care of. ### Do I need to know how to code? No. The agents handle the technical work. You tell your own agent or Kamu what you want, or edit texts directly in the dashboard. If you do code, the site is a standard Astro codebase, and you can request git access to it. ### Can I use my own AI agent? Yes. Connect any MCP client to `https://mcp.kamu.build`. You choose what it may read, edit and publish. Its model use is paid to your own AI provider, and it uses no agent credit. Read more: [Your own AI agent (MCP)](/mcp/overview) ### How quickly is the site ready? When Kamu builds the first site, it usually takes 20-30 minutes. You can follow the progress in the dashboard in real time. Subsequent updates are usually completed in 15-20 minutes. Changes made in [Studio](/editing/studio) show up in the preview right away. ### Can I try the service for free? Yes. The trial is free and requires no payment card. You can create up to five trial sites, and they work at the address `{site}.kskamu.app`. A plan is only needed when you want to connect your own domain to the site. The first build of a site is free. Each new user also gets 5 EUR of [agent credit](/billing/agent-credit) for editing the site with Kamu in Studio. ### How long is the trial? The trial lasts 30 days from your latest activity: building the site, editing it, or topping up your agent credit. You'll get an email reminder before it ends. The site of an expired trial is no longer visible, but it is kept for 90 days, and you can restore it by ordering a plan for it or by contacting support. ## Site ### Can I edit the site myself? Yes, in four ways: 1. **With your own AI agent**: connect it over [MCP](/mcp/overview) and ask it to make the changes 2. **In [Studio](/editing/studio)**: tell Kamu what you want to change, see the changes in the preview right away, and publish when you're happy 3. **With the [Assistant](/editing/chat)**: send a single change request in a conversation, and the site builder makes the update 4. **By hand**: edit texts on the [Texts](/editing/texts) page and blog posts on the [Posts](/editing/blog-posts) page Studio and updates started from the Assistant use [agent credit](/billing/agent-credit). Editing texts and blog posts by hand is free, and so is editing with your own agent. ### Can I use my own images? Yes. You can upload images to the Media page in the dashboard or attach them directly to a message in Studio or the Assistant. Read more: [Images and media](/site/images-and-media) ### Is the site mobile-friendly? Yes. All sites work smoothly on phones, tablets, and desktops. ### How does my site get found on Google? Sites are built with search engine optimization (SEO). The site is automatically indexed by Google, usually within a few days. On the site's **Search engines** page you can see how the site shows up in Google and AI search, and some of the issues found can be fixed with the **Fix** button. Visibility improves when your contact details and opening hours on the site are up to date. You change them by asking Kamu in Studio or the Assistant, or your own agent. A business that serves a local area should also set up a [Google Business Profile](/site/google-business-profile). ### Can I add a blog to my site? Yes. Request blog addition from the Assistant page. You can publish new blog posts using the chat tool or manage them from the Posts page. ### Will I be notified about contact requests? Yes. You can receive notifications via email, browser push notifications, and WhatsApp. Read more: [Notifications](/site/notifications) ## Domain ### Do I need my own domain? Your site automatically gets an address like `{site}.kskamu.app`. If you want your own domain (e.g., `company.com`), you can connect it from the dashboard. Connecting your own domain requires a paid plan. You can buy a domain during the trial and connect it to the site later. ### Where can I get a domain? You can register a new domain at [kamu.build/domains](https://kamu.build/domains) or from the **Domains** page in the dashboard. You can also connect a domain you bought from another registrar. ### How do I connect a domain? See instructions at [Domain management](/domains/your-domain). ## Billing ### How much does a plan cost? - **Lite**: 3.90 EUR/mo, billed yearly at 46.80 EUR. No monthly agent credit; you top up when needed. - **Pro**: 13.99 EUR/mo billed monthly, or 9.99 EUR/mo billed yearly (119.88 EUR). Includes 10 EUR of agent credit per month. Prices exclude VAT, which is added at checkout according to your country. EU businesses with a valid VAT ID are reverse-charged. A domain is not included in any plan; it is ordered separately. The trial is free. Read more: [Plans](/billing/plans) ### Can I cancel my subscription? Yes. On the site's **Settings** page, under **Subscription**, press **Cancel subscription**. The cancellation request goes to support, and we will contact you to process it. The site remains active until the end of the billing period. ### How do I pay invoices? You'll receive the invoice by email and can pay it by bank transfer. An open invoice can also be paid by card with the **Pay by card** button on the dashboard's Billing page. If you save a payment card on the Billing page and turn on automatic charge, invoices are charged to the card on their due date. Read more: [Invoices](/billing/invoices) ### What is agent credit? Agent credit is a team-wide prepaid balance. It pays for site updates after the free first build, edits in Studio and with Kamu, documents, and logo generation. Editing texts and blog posts by hand is free, and so is editing with your own agent over MCP. A new user gets 5 EUR of welcome credit, and the Pro plan adds 10 EUR per site every month. Lite and the trial include no monthly credit. You can top up from the Billing page. Read more: [Agent credit](/billing/agent-credit) ## Team ### Can I invite other users? Yes. You can invite team members from the Team page by email. Team members have access to all of the team's sites. To give access to a single site only, invite the user from the site's **Users** page. A site-specific user does not see the team's other sites. This also suits an agency that edits the site with its own AI agent. ### Can I manage multiple sites? Yes. With one account you can manage multiple sites. Sites are shown by team in the dashboard. ## Support ### How do I get help? - **Support button**: in the bottom right corner of the dashboard (**?** button). You can ask the AI assistant, which answers right away, or send a message to our team. We respond to support messages within 24 hours, usually much faster. - **Contact page**: [kamu.build/contact](https://kamu.build/contact) - **WhatsApp**: you can also manage your site via WhatsApp - **Docs**: [docs.kamu.build](https://docs.kamu.build) --- # Plans Each site has its own plan. The options are the free **Trial** and the paid **Lite** and **Pro** plans. The same prices are on [kamu.build/pricing](https://kamu.build/pricing). ## Trial period The trial is free and does not require a payment card. During the trial: - The site is available at `{site}.kskamu.app` - You can edit the site normally. AI edits use [agent credit](/billing/agent-credit), and you can use the welcome credit for them. Edits your own AI agent makes over MCP use no agent credit - Connecting your own domain is not possible The trial is valid for **30 days from the last edit**. The period is extended whenever the site is built or edited or you top up agent credit. You get an email reminder 7 and 2 days before the trial ends. When the trial ends, the site is taken offline. The site and its content are kept for another 90 days, and you get a notice before permanent deletion. During that time you can restore the site by ordering a plan, and it comes back at the same address. One user can create up to 5 trial sites. After that, a new site is created directly on the Pro plan. ## Plan options | | Lite | Pro, monthly | Pro, yearly | |---|---|---|---| | Price (excl. VAT) | 3.90 €/mo | 13.99 €/mo | 9.99 €/mo | | Billing | 46.80 € per year | monthly | 119.88 € per year | | Monthly agent credit | no | 10 € | 10 € | Lite is billed yearly only. Prices are per site and exclude VAT. VAT is added at checkout according to your country, and EU businesses with a valid VAT ID are reverse-charged (see [Updating billing details](/billing/invoices#updating-billing-details)). On the order page you can switch the prices between excluding and including VAT. ## What's included All paid plans include: - Hosting and maintenance - SSL certificate (HTTPS) - Contact form and other forms - Cookie-free visitor analytics - Custom domain connection - The free [blog](/editing/blog-posts) and [text](/editing/texts) editors - Editing through your own AI agent over [MCP](/mcp/overview) AI edits by Kamu and site updates are charged to [agent credit](/billing/agent-credit) on every plan. The Pro plan includes 10 € of agent credit every month. Lite suits a site that is updated rarely; credit for its edits is topped up separately. A domain is not included in the plan; it is ordered and invoiced separately. ## Ordering a plan When the site is ready to go live, open the **Take the site into use** order page. You get there from the site overview, through connecting a domain, or from the page of an ended trial (**Order a plan**). 1. **Domain**: search for and choose a new domain, or continue without one if you already have your own domain or don't need one yet. You can [connect](/domains/connecting) your own domain later. 2. **Plan**: choose Lite, Pro (monthly or yearly billing), or the trial. With Lite and the trial you can top up agent credit at the same time. 3. **Payment**: review the order and save a payment card. Saving the card does not charge anything by itself. The order is confirmed right away. It produces a single invoice, charged to the card you saved, usually within a few minutes. New domains are registered once the invoice is paid. You can find the invoice in the [Invoices](/billing/invoices) section. If invoicing without a card has been agreed for your team, no card is asked for. You then get an invoice with a 14-day payment term, and domains are registered once it is paid. ### Orders started by your AI agent A connected AI agent with the Domains and orders extra permission can start an order for a plan, domains, or both, and give you a link to the order page. You check the order, fill in the billing details, accept the terms and confirm it yourself. Nothing is charged before you confirm. See [Ordering a plan and a domain](/mcp/overview#ordering-a-plan-and-a-domain). ## Managing your subscription You can see the site's plan and price on the site's **Settings** page under **Subscription**. From there you can also go to the **Billing** page, whose **Subscriptions** section lists all of the team's sites with their plans. To switch from one paid plan to another, for example from monthly to yearly billing, contact customer support. ## Cancelling a subscription Press **Cancel subscription** under **Subscription** in the site settings and confirm with **Send a cancellation request**. The request goes to customer support, who will contact you to process the cancellation. ## Deleting a site You can delete a site entirely from the site settings under **Delete site**. After deletion, the site can be recovered within 7 days. After that, the site and all its data are permanently deleted. --- # Invoices You can find all your invoices on the **Billing** page in the dashboard. ## The Billing page The Billing page has four sections: - **Agent credit**: credit status and top-ups, see [Agent credit](/billing/agent-credit) - **Subscriptions**: the team's sites, their plans and prices, and the monthly total - **Payment card**: the saved card and automatic charging - **Invoices**: all invoices and receipts The Invoices section header shows the total of open invoices. Use the search field to find an invoice by invoice number, reference number, or additional details. For each invoice you can see: - Invoice number - Invoice date and due date - Amount - Status (draft / sent / paid / overdue) Click an invoice to open it and see the invoice lines with VAT. A finished invoice can be downloaded as a PDF with the **Download PDF** button. Agent credit top-ups and purchases paid by card produce a **receipt**, shown in the same list. A receipt can be downloaded as a PDF. ## Paying The payment term is 14 days. An open invoice can be paid in three ways: - **By bank transfer**: the invoice is delivered by email, and you pay it with the invoice details. - **By card**: press **Pay by card** next to the invoice. Payment is made via Stripe, and the invoice is marked paid as soon as the payment is confirmed. - **Automatically from your card**: if automatic charging is on, the invoice is charged to the saved card on the due date (see below). ## Payment card and automatic charging In the **Payment card** section you can save a card by pressing **Add a payment card**. Saving a card does not charge anything. Once a card is saved, the **Automatic charge** switch decides whether invoices that fall due are charged to the card on the due date. The invoice is visible on the Billing page before the charge, and you can pay it yourself before the due date. - If you save a card yourself on the Billing page, automatic charging starts switched off. - If you order a plan or a domain by card, automatic charging is switched on. That way the order's invoice and the plan's renewals are charged to the card. You can switch charging off or remove the card (**Delete card**) at any time. Invoices are then paid by bank transfer or with the **Pay by card** button. ## Invoicing without a card If your company wants to pay invoices by bank transfer and not save a card, contact customer support (the support button in the dashboard, or the [contact page](https://kamu.build/contact)). We can enable invoicing without a card for the team; orders are then confirmed right away and the invoice is sent with a 14-day payment term. ## Updating billing details Billing details are managed in the **Team details** section of the **Team** page. Only the team owner or an admin can edit them. Update there: - Country. The country determines which billing details are needed and which VAT applies. - Account type (business / individual) - Official company name - Address, postal code, and city - VAT ID, if the company is in the EU. When the ID is found in the VIES register and the company is outside Finland, we invoice without VAT (reverse charge). Otherwise VAT is added according to your country. - **Invoice delivery**: email. Finnish companies can also choose e-invoice. If you leave the billing email empty, invoices go to the account owner's email. ## Choosing a team If you belong to multiple teams, you can switch teams from the top right corner of the Billing page. Invoices and agent credit are shown per team. --- # Agent credit Agent credit is the prepaid balance consumed by site builds and by Kamu's AI editing in [Studio](/editing/studio). Talking to Kamu in the [Chat view](/editing/chat) or on WhatsApp is free; credit is used only when a site update is started from the conversation. The [blog editor](/editing/blog-posts) and the [text editor](/editing/texts) are also free on every plan. The credit is shown in euros on the **Billing** page in the dashboard and in the Studio top bar. Your own AI agent connected over [MCP](/mcp/overview) uses no agent credit. Its model use is paid to your own AI provider. Agent credit is **team-wide**: one shared balance covers all of the team's sites and users. ## Where the credit comes from - **Welcome credit**: every new user gets 5 € of agent credit once, on signup. - **Included in the Pro plan**: every site on the Pro plan adds 10 € to the team's credit every month, counted from the plan start date, whether the plan is billed monthly or yearly. The credit accumulates; unused credit does not disappear at the end of the month. - **Top-ups**: you can top up at any time (see below). The Lite plan and the trial do not include monthly credit. On them, edits are paid from the welcome credit and from credit you top up yourself. All credit is valid for **12 months** from the day it was added, and the oldest credit is used first. ## What the credit is spent on - **Studio sessions.** The price is based on the tokens used; Studio machine time is not charged. A typical editing session costs 1-3 €. - **Site builds and updates.** The first successful build of a site is free. After that every new build and update, including ones started from the conversation, is charged to the credit according to actual usage. Failed builds are not charged. - **Logo generation** by the chat assistant, 0.10 € each. - **[Documents](/documents)**: documents made with Kamu use the credit the same way Studio does. A build that has started runs to the end, even if the credit does not cover it. The balance can then go negative, and the next top-up or monthly credit covers the difference first. ## Topping up 1. Open the **Billing** page and press the top-up button on the agent credit card. 2. Choose an amount: 10 €, 25 €, 50 €, or another amount between 1 and 500 €. 3. Press **Continue to payment**. Payment is made by card via Stripe. The credit updates shortly after payment, and a receipt for the top-up appears among your invoices. The amount includes VAT. You can also top up when ordering a plan, if you choose the Lite plan or the trial. ## Credit status The agent credit card on the Billing page shows: - the total credit and its status (**OK**, **Running low**, **Out of balance**, or **Negative**) - the amount and date of the next batch to expire - behind the **Show top-ups** link, every batch (welcome balance, monthly balance, top-up, or credit), how much of it remains, and its expiry date. ## Tracking consumption The **View usage** link on the agent credit card opens the **Usage** page, where you can see what the credit has been spent on: - Choose the period with the **From** and **Until** fields. You can also filter by source and by site. - You can see the time, source (for example a Studio session or a site build), site, and amount of each event. A Studio session's rows are grouped together, so you see the session's total cost on one line. - The **By day** button groups consumption per day. - **Export CSV** downloads the rows as a spreadsheet file. The team settings page also has a summary of the last 30 days' usage. ## When the credit is low - When less than 3 € remains, the agent credit card shows the status **Running low**. - When the credit is empty or negative, Studio cannot be opened and a new build cannot be started until you top up. A site's first build still goes through. - If the credit runs out while you are using Studio, Kamu cannot continue. The changes already made are kept, and you can save and publish them. Top up in another tab and reload the Studio page. --- # Domain management From the **Domains** page in the top bar you can register new domains, transfer existing ones, and manage all your domains. If you belong to several teams, domains are listed per team. You can also search domains before signing up at [kamu.build/domains](https://kamu.build/domains). ## Registering a new domain 1. Go to the **Domains** page and click **Get domain** 2. Type the name you want in the search field (e.g. `examplecompany` or `examplecompany.com`) and search 3. You'll see available domains across many extensions (.com, .net, .org, .eu, .io, .dev, .app, country domains and more), with their prices and renewal prices 4. Click **Add** next to the domain you want. One order can hold up to five domains 5. Click **Continue to checkout**, fill in the domain owner's details and accept the terms 6. Click **Confirm the order** The owner details asked are name, address, email and phone number. Prices are in euros, and VAT is added according to your country at checkout (EU businesses with a valid VAT number: reverse charge). If your team has no saved payment card, you'll be asked to save one. Saving the card does not charge anything by itself. :::note[.fi domains] A .fi domain also needs a business ID (company) or personal ID (private person) of the owner, and WHOIS protection is not available for it. ::: ### The domain is registered once the invoice is paid The order creates an invoice, and the domain is registered only after the invoice has been paid. With card payment this usually happens within a few minutes. Until then the domain's status is **Awaiting payment**. If the invoice is not paid within 30 days, the registration is cancelled and the status becomes **Cancelled**. ## The domain page Clicking a domain in the list shows its details and settings: - **Valid**: the date the domain is valid until - **Automatic renewal**: when renewal is on, an invoice for the renewal is created about two months before the domain expires. If you turn renewal off, the domain is released unless you renew it yourself - **WHOIS protection**: hides the owner's contact details from public WHOIS lookups - **Transfer to another registrar**: the transfer code and transfer lock, if you want to move the domain elsewhere. See [Domain transfer](/domains/transfer#transferring-away-from-kamubuild) - **Team**: the domain can be moved to another team if you are an administrator in both teams - **Connect to site**: connecting the domain to a site. See [Connecting to a site](/domains/connecting) The same page also holds [Email](/domains/email), redirects, and [DNS records and nameservers](/domains/dns-settings#kamu-dns). Only team administrators can change a domain's settings. ## Domain transfer If you already have a domain with another registrar, you can transfer it to Kamu.build. See [Domain transfer](/domains/transfer). ## Connecting a domain to your site Once you have a domain, you can connect it to your site. See [Connecting to a site](/domains/connecting). ## Can I use a domain registered elsewhere? Yes. You don't have to register or transfer a domain through Kamu.build. You can use a domain from any registrar and set the [DNS records](/domains/dns-settings) yourself at your DNS provider. Email forwarding, SMTP credentials and the BIMI logo are available only for domains registered or transferred through Kamu.build. --- # Domain transfer If you already have a domain with another registrar (e.g. GoDaddy, Namecheap, Cloudflare), you can transfer it to Kamu.build. After the transfer, the site's DNS settings can be configured automatically. :::tip[Need help?] If you'd rather not do it yourself, [contact us](https://kamu.build/contact). Once you have the transfer code, we can handle the transfer for you. ::: ## How does the transfer work? A transfer changes the domain's registrar from your current provider to the registrar Kamu.build uses. The domain and its services (such as email and website) keep working normally during the transfer. ## What do you need? 1. **A transfer code** (EPP / Auth Code) from your current registrar. You usually find it in the registrar's dashboard, often under the domain's transfer settings. If you can't find it, ask the registrar's support 2. **Access to the domain owner's email**. Both the current and the new owner may receive a confirmation email that must be approved 3. **The transfer lock removed** at your current registrar (Registry Lock / Domain Lock / `clientTransferProhibited`). The transfer won't go through while the lock is on ## Making the transfer 1. Go to the **Domains** page in the dashboard 2. Click **Transfer domain** 3. Enter the domain (e.g. `company.com`). You'll see the transfer price, and the dashboard fetches the domain's current public DNS records 4. Enter the transfer code 5. Choose which DNS records to import with the transfer (see [DNS records and email](#dns-records-and-email)) 6. Fill in the owner details 7. Click **Start transfer**, or for a paid transfer **Pay ... € and start transfer** If the domain is not registered at all, it cannot be transferred. The dashboard then offers to register it as new. ## Pricing The transfer is charged at the registrar's transfer fee with no markup, plus VAT according to your country. For most extensions (.com, .net, .org and so on) the transfer extends the domain by one year. The dashboard shows the price and the renewal price before you start. The domain is renewed automatically after the transfer. :::note[.fi domains] A .fi transfer is free and keeps the current validity. The code is called a transfer key, and the transfer usually completes within hours. ::: ## How long does the transfer take? For most extensions, up to 5–7 days, because the transfer needs confirmations from both registrars. During the transfer, the domain's page shows the transfer status. Your current registrar may require a separate approval in its own dashboard. If the transfer doesn't progress, check whether it is waiting for your approval there. If the transfer fails, for example because of a wrong transfer code, the domain's page shows the latest error. You can correct the transfer code or the owner details and click **Save and try again**. ## DNS records and email The transfer form fetches the domain's current public DNS records and lists them. Choose which records to import. Some records are not publicly visible and cannot be fetched automatically. You can add missing records by pasting them as text (**Paste records (zonefile)**) or from a file (**Import from a file**). Nameserver records are not imported. If the dashboard recognises the service your nameservers are at (e.g. Cloudflare), you can choose to keep the nameservers there. The DNS settings then stay as they are, and only the registrar changes. :::warning[Important] If your domain is connected to an email service (e.g. Google Workspace, Microsoft 365) or other services, check before the transfer that all necessary DNS records (MX, TXT, CNAME) are in the list to import. A screenshot or export of your current records is a good backup. If you're unsure, [contact us](https://kamu.build/contact) before the transfer and we'll check together that no service is interrupted. ::: ## After the transfer Once the transfer is complete, the domain appears on the **Domains** page with the status **Active**. You can then [connect it to your site](/domains/connecting). If DNS records were imported with the transfer, the nameservers are switched to ours and the site's DNS settings are configured automatically. If you kept the nameservers at your previous service, you set the [DNS records](/domains/dns-settings) there yourself. ## Transferring away from Kamu.build {#transferring-away-from-kamubuild} You can transfer the domain to another registrar at any time: 1. Open the domain's page and, under **Transfer to another registrar**, click **Show transfer code** 2. Copy the transfer code 3. If the transfer lock is on, click **Remove lock** 4. Start the transfer at the new registrar The transfer code is valid for a limited time, so fetch it only when you start the transfer. --- # Connecting a domain to your site Once you have a domain, you can connect it to your site. Connecting your own domain requires a paid plan. ## Plan required If your site is still on its trial period, the site's **Domains** page shows an **Update subscription** card with a button to choose a plan. There you choose a plan and, if you like, a new domain in the same order. Plans and prices are on the [Plans](/billing/plans) page and at [kamu.build/pricing](https://kamu.build/pricing). Before connecting, the dashboard asks you to check the team's billing details. Only the team owner or an administrator can complete them. The site must also have been published once before a domain can be connected. ## Adding a domain to your site 1. Open your site in the dashboard 2. Go to the **Domains** page in the **Management** section 3. Pick one of your team's domains from the list, or enter a domain without the www prefix (e.g. `company.com`), and click **Connect** If you entered a domain held elsewhere, the dashboard shows its registrar and current nameservers, and where its DNS is probably managed. You can then: - **Transfer domain** to Kamu.build, so DNS settings and renewal are handled for you. See [Domain transfer](/domains/transfer) - Keep the domain at its current provider and point its DNS records to us yourself. See [DNS settings](/domains/dns-settings) If you need help, [contact us](https://kamu.build/contact). If the domain is still available, the dashboard offers to register it. A team domain can also be connected from its own page under **Domains** in the top bar (**Connect to site**). A domain whose registration or transfer is still in progress cannot be connected yet. A site has one primary domain. ## DNS settings After you add the domain to your site, it needs to point to our servers. How depends on where the domain is held. ### Domain registered or transferred through Kamu.build DNS settings are configured automatically when the domain's nameservers are ours. If you kept the nameservers at your previous provider during the transfer, you set the records there yourself. ### Domain registered elsewhere You make the DNS changes yourself at your DNS provider. The site's Domains page shows the required records and their current values. See [DNS settings](/domains/dns-settings). The domain's status is **Awaiting verification** until DNS points correctly. You can check it with **Check status**. When the status is **Active**, the domain is in use. ## SSL certificate An SSL certificate (HTTPS) is created automatically once DNS is correct. This may take a few minutes. ## Other domains for the same site Once the primary domain is active, the site's Domains page shows an **Other domains** card. There you can point your team's other domains (e.g. `company.net`) to this site. Visitors are redirected permanently (301) to the primary address. If the nameservers of the redirected domain are not yet ours, they are switched at the same time. Any other DNS records of that domain, such as email, then stop working unless they were imported into the domain's DNS records first. ## Removing a domain from the site A connected domain can be removed on the site's Domains page. While DNS still points to us, the site keeps showing at that address until the DNS records are removed. --- # DNS settings If your domain's DNS is managed elsewhere than at Kamu.build, you make the DNS changes yourself at your DNS provider. :::info[Domains registered through Kamu.build] If you registered or transferred your domain through Kamu.build and its nameservers are ours, the site's DNS settings are configured automatically. You can manage other records in the dashboard, see [DNS for a domain held at Kamu.build](#kamu-dns). ::: ## A record (required) | Type | Name | Value | |------|------|-------| | A | @ | 137.66.10.148 | This points the root domain (e.g. `company.com`) to your site. ## AAAA record (recommended) For IPv6: | Type | Name | Value | |------|------|-------| | AAAA | @ | 2a09:8280:1::dd:6148:0 | ## WWW redirect The site works on the root domain (e.g. `company.com`). If you also want `www.company.com` to work, add the same records for www: | Type | Name | Value | |------|------|-------| | A | www | 137.66.10.148 | | AAAA | www | 2a09:8280:1::dd:6148:0 | `www.company.com` is redirected to `company.com` automatically (301). You don't need to set up a separate redirect. :::tip[Alternatively CNAME] Instead of A and AAAA records, you can use a CNAME record for www: | Type | Name | Value | |------|------|-------| | CNAME | www | company.com | This works just as well, as long as the root domain's A record is in place. ::: ### What if I want the www form as primary? The site uses the root domain as its primary address, and the domain is entered in the dashboard without the www prefix. If you want the www form as primary, [contact us](https://kamu.build/contact). ## DNS propagation DNS changes can take up to 24 hours, but usually they take effect within a few minutes. ## Where are DNS settings configured? It depends on the provider. Look for a section like "DNS", "Nameservers" or "Domain settings" in its dashboard, for example: - **Cloudflare**: dash.cloudflare.com - **Namecheap**: namecheap.com - **GoDaddy**: godaddy.com ## DNS for a domain held at Kamu.build {#kamu-dns} DNS records of domains registered or transferred through Kamu.build are managed on the domain's page (**Domains** in the top bar, then select the domain). ### DNS records In the **DNS records** card you can add, edit and delete records. You can also import records: - **Import the current records** fetches the domain's publicly visible records from the current provider - **Import from text or a screenshot** recognises records from pasted text or a screenshot, for example from an email service's setup instructions - **Import from a file** imports records from a zonefile **Export** saves the records as a file. ### Nameservers {#nameservers} The records are in effect only when the domain's nameservers point to our nameservers (KamuDNS). If they point elsewhere, the page shows a warning and the button **Switch to the KamuDNS nameservers**. You can edit the records in advance before switching. :::warning[Import the records before switching] Before switching nameservers, check that the DNS records card holds all records from your current provider, especially the email MX and TXT records. Otherwise your site or email may stop working. ::: In the **Nameservers** card you can also set your own nameservers (at least two). After a change, the card shows the requested nameservers and the ones in force at the registry separately. The change usually shows up at the registry within a few hours, at most 48 hours. Until then the domain uses the old nameservers. ### Redirects In the **Redirects** card you can redirect the domain, or a subdomain and path, to another address, either permanently (301) or temporarily (302). Redirects work only when the nameservers point to KamuDNS. --- # Email for your domain Email is set up in the dashboard under **Domains**, then the domain, then **Email**. There are two options: our forwarding and outgoing mail server, or another provider such as Microsoft 365 or Google Workspace. The Email card is available for domains registered or transferred through Kamu.build. The settings are in effect when the domain's nameservers are ours (see [Nameservers](/domains/dns-settings#nameservers)). Only team administrators can change the settings. ## Option 1: Forwarding and SMTP from us Kamu.build offers two services: 1. **Incoming mail forwarding.** Mail sent to an address such as `info@yourcompany.com` is forwarded to an existing mailbox you specify (e.g. `firstname.lastname@gmail.com`). 2. **Outgoing SMTP server.** You can send messages from an `@yourcompany.com` address through Gmail or Outlook, for example, so the recipient sees the correct sender. :::info[No mailboxes] We do not store email. You need a regular email service (e.g. Gmail) that messages are forwarded to and that you send from. ::: When you choose this option, we add the required DNS records automatically as you start using the services: | Type | Name | Purpose | Added when | |--------|------|-----------|------------| | MX | @ | Receives incoming mail on our server | there is at least one forward | | TXT | @ | SPF record (allows our servers to send mail on your behalf) | there is a forward or an SMTP credential | | TXT | _dmarc | DMARC policy | there is an SMTP credential | | CNAME | *._domainkey | DKIM keys for signing outgoing mail | there is an SMTP credential | If records have gone missing or were deleted by accident, **Update DNS** adds them again. ### Adding a forward 1. Open the domain's **Email** card. 2. In **Source address**, enter the first part of the address (e.g. `info`, or `*` for all addresses). 3. In **Email addresses**, enter one or more destination addresses separated by commas. 4. Click **Add a forward**. The forward is active as soon as the DNS records have propagated (usually minutes). You can edit a forward's destinations later, and switch a forward off temporarily without deleting it. ### Gmail: send from your @yourcompany.com address The most common setup: you read mail in Gmail but want to send from your business address. #### 1. Create SMTP credentials in the dashboard 1. In the Email card, enter the address you want to send from (e.g. `info`) in **Sender address** and click **Create SMTP credentials**. 2. Save the **username** and **password** immediately. The password is not shown again; if you lose it, create new credentials. The server is `mail.kotisivukamu.fi`, port `587` (STARTTLS). Port `465` (SSL/TLS) also works. Each credential is tied to one sender address. To send from several addresses (e.g. `info@` and `sales@`), create credentials for each. #### 2. Add the address to Gmail 1. Open [Gmail settings](https://mail.google.com/mail/u/0/#settings/accounts) → **Accounts and Import** → **Send mail as** → **Add another email address**. 2. Enter: - **Name**: the name you want recipients to see - **Email address**: e.g. `info@yourcompany.com` - **Treat as an alias**: untick if you want replies to come to Gmail while the "From" field shows correctly. 3. **Next Step**. Gmail asks for the SMTP settings: - **SMTP Server**: `mail.kotisivukamu.fi` - **Port**: `587` - **Username** and **Password**: the credentials you created - **Secured connection using TLS**: selected 4. Gmail sends a verification code to `info@yourcompany.com`. Because forwarding is set up, the code arrives in your Gmail. Copy it and confirm. When composing a message, you can now choose the sender address in the **From** field. #### Other email clients - **Outlook.com / Microsoft 365**: Settings → Mail → Sync email → Connected accounts → new POP/SMTP account. - **Apple Mail (macOS/iOS)**: Mail → Settings → Accounts → new Other Mail Account, with the same SMTP settings. - **Mozilla Thunderbird**: Account Settings → Outgoing Server (SMTP) → Add. The settings are the same everywhere: server `mail.kotisivukamu.fi`, port `587` (STARTTLS) or `465` (SSL/TLS). ### Forwarding as a webhook Email can also be forwarded to your own service as an HTTP POST request, for example to open a customer's message directly in your ticketing system or CRM without a mailbox in between. 1. Create a forward with a **Source address** (e.g. `support`) and a **Webhook URL** (e.g. `https://yourservice.com/incoming-email`). Leave the destination addresses empty if you want *only* the webhook, or fill in both so the message is both forwarded and POSTed. 2. Save. When a message arrives, we parse the MIME body and send a JSON request to your webhook in this format: ```json { "from": "sender@example.com", "to": ["support@yourcompany.com"], "to_local": "support@yourcompany.com", "subject": "Order status", "messageId": "", "date": "Mon, 20 Apr 2026 19:00:00 +0000", "headers": { "...": "all headers" }, "body": { "text": "Plain text...", "html": "

HTML...

" }, "attachments": [ { "filename": "attachment.pdf", "contentType": "application/pdf", "size": 12345, "content": "base64..." } ], "authentication": { "spf": {...}, "dkim": {...}, "dmarc": {...} } } ``` Your server must respond with a `2xx` status within 20 seconds. Otherwise we retry up to three times with increasing delays. `4xx` responses are not retried, since they point to a configuration error rather than a temporary fault. :::tip Use an HTTPS address only. Attachments arrive base64-encoded inside the JSON body, so a single parse handles everything. ::: ### Limits - Destination addresses: up to 10 per forward. - Maximum message size: **50 MB** (headers, body and attachments combined). Larger messages are rejected before forwarding. The practical limit for a message forwarded to an email address is about 40 MB; a message delivered to a webhook can be 50 MB. - Outgoing messages: about 30 per minute per SMTP credential. The service is meant for ordinary business email, not bulk mailings. ## Option 2: Another provider If you use Google Workspace, Microsoft 365 or another email service, choose **Another provider** in the Email card. We then do not add or remove email-related DNS records automatically. ### Microsoft 365 and Google Workspace For Microsoft 365 and Google Workspace the Email card has the buttons **Set up Microsoft 365** and **Set up Google Workspace**. They add the records the service needs for you. The buttons show when the domain's nameservers are ours. 1. Add the domain in the service's admin console. The service shows the DNS records it needs. 2. Copy the records into the dialog as text or paste a screenshot. The dialog shows which records will be added, which already exist and which are missing. At minimum the ownership verification record (TXT) and the incoming mail MX record must be included. 3. Save, and verify the domain in the service. Microsoft 365 shows the rest of the records only after verification, so its setup has two steps: first the verification record, then the other records. Old conflicting records, such as a previous MX record, are removed, and the dialog shows them before you save. If the domain has no DMARC record, we add a default one. ### Other services 1. Sign up for the service of your choice with your domain. 2. The service gives you a list of DNS records (MX, SPF, usually also DKIM). 3. Add the records in the **DNS records** card on the domain's page. **Import from text or a screenshot** recognises the records from the service's instructions, so you don't have to type them by hand. 4. The service verifies the records, usually within a few minutes. :::tip[Need help?] If adding the records doesn't work out, [contact us](https://kamu.build/contact) and we'll add them for you. ::: --- # BIMI logo for email BIMI (Brand Indicators for Message Identification) shows your company's logo next to the sender name in the recipient's inbox. It only works in supported email clients and requires that the domain's DMARC policy is at least **Quarantine** (`p=quarantine`). You can add a BIMI logo when: - the domain is registered or transferred through Kamu.build and our forwarding and SMTP is chosen as its email option (see [Email](/domains/email)) - you send mail with one of our SMTP credentials, because the DMARC record is published only once the domain has an SMTP credential - the domain is connected to a site, because the logo is published at your site's address ## Where the logo shows | Email client | Shows without a VMC certificate | Requires a VMC certificate | |-------------------|--------------------------------|------------------------| | Fastmail | Yes | – | | Mail.ru | Yes | – | | La Poste | Yes | – | | Gmail (Workspace & free) | No | Yes | | Apple Mail (iOS 16+, macOS Ventura+) | No | Yes | | Yahoo | No | Yes | **VMC (Verified Mark Certificate)** is a third-party certificate (DigiCert, Entrust) that verifies the logo is your registered trademark. It costs around 1,200–1,500 euros per year. We do not resell VMC certificates. If you want Gmail visibility, obtain the certificate yourself and [contact us](https://kamu.build/contact) so we can add it to the BIMI record. ## SVG Tiny P/S requirements A BIMI logo must be an SVG, but not just any SVG. The profile is called **SVG Tiny 1.2 Portable/Secure**, and its requirements are strict because email services must not load external resources or run scripts. ### Required - The root `` element contains the attributes: - `version="1.2"` - `baseProfile="tiny-ps"` - `xmlns="http://www.w3.org/2000/svg"` - a `viewBox` whose width and height are **equal** (square) - Exactly one `` element inside the `` (not empty, e.g. your brand name) - The file saved as **UTF-8** without a BOM - Size at most **32 KB** (recommended under 10 KB) ### Forbidden - DOCTYPE or external entities - Elements: `