# Laarpi

> Laarpi takes a website from a thought to a finished, live site in one place: designed from scratch with real 3D, motion and type, shipped to your domain.

Laarpi is a coding agent for websites. Its agent is called SI: automated software that runs on AI models from third-party providers. You describe a site; the agent asks the few questions that matter, writes a plan you can edit, builds the site live in front of you, takes direction in plain words or by pointing at any part of the page, and ships it to a Laarpi subdomain or your own domain.

Every site is designed from scratch around the idea, with real-time 3D (three.js / WebGL), motion with intent and typography with a voice. No templates. Sign-in, data and payments are wired in by connecting your own Supabase and Polar accounts. The sites are plain HTML, CSS and JavaScript.

The steps are: Ask, Brief, Build, Direct, Ship. The primary action on the site is Start building.

## About Laarpi

- [About](http://localhost:3000/about): The people and company behind Laarpi, what ships today, and the editorial policy behind every page on this site.
- [Contact](http://localhost:3000/contact): Write to the Laarpi team about your account, billing, press or a security issue. To have a site built with us, use the Build with experts form so we get the details we need.
- [How it works](http://localhost:3000/how-it-works): Laarpi's agent, SI, asks what matters, writes a brief you can edit, builds the site in front of you, checks its own work, and publishes it. What happens at each step, and what you control.
- [Privacy](http://localhost:3000/privacy): How Laarpi handles personal data, in plain language: what we collect, how the agent's AI processing works, what lives in your own accounts, the few cookies we set, how long we keep things, and your rights. Draft pending legal review.
- [Refunds](http://localhost:3000/refunds): When you can get money back for a Laarpi plan, how to ask, and how Polar, our merchant of record, processes it. Written in plain language. Draft pending legal review.
- [Terms](http://localhost:3000/terms): The agreement between you and Laarpi, written in plain language: what you own, what we do, how plans and credits work, and what is not allowed. This is a draft pending legal review.
- [Pricing](http://localhost:3000/pricing): plans in US dollars and euros, with special pricing in India.
- [Community](http://localhost:3000/community): The showcase sites were made by the Laarpi team with Laarpi’s library and process. Open any of them live, or remix one into a site of your own.

## Pricing

Prices are in US dollars, or in euros across the EU and in Iceland, Liechtenstein, Norway and Switzerland; India has its own prices, in rupees. Visitors can change the currency on the pricing page. Checkout runs through Polar, which adds VAT or sales tax where it applies.

- Free: $0 or €0 (₹0 in India). Start building. The first sites are on us. Includes 30 credits a month, a Laarpi subdomain, a small "Made with Laarpi" badge.
- Pro: $25 or €25/month, or $20 or €20/month billed yearly (India: ₹999/month, or ₹799/month billed yearly). For people who ship. Includes 250 credits a month, 3 custom domains, no badge. Code download is planned and not yet available.
- Max: $100 or €100/month, or $80 or €80/month billed yearly (India: ₹3,999/month, or ₹3,199/month billed yearly). For heavy builders and freelancers. Includes 1,200 credits a month, 10 custom domains, no badge. Code download is planned and not yet available.
- Max (larger size): $200 or €200/month, or $160 or €160/month billed yearly (India: ₹7,999/month, or ₹6,399/month billed yearly). For heavy builders and freelancers. Includes 2,800 credits a month, 10 custom domains, no badge. Code download is planned and not yet available.
- Business: $50 or €50/month per seat, or $40 or €40/month per seat billed yearly (India: ₹1,999/month, or ₹1,599/month billed yearly). For teams building together. Includes 600 credits a month per seat, 25 custom domains, one credit pool shared by every seat, no badge. Code download is planned and not yet available.
- Build with experts: custom quote. Tell us your idea. Our team builds it with Laarpi and hands it over. See http://localhost:3000/experts

Credits are metered by what each agent turn really costs. Remixing a community site costs no credits.

## Features

- [All features](http://localhost:3000/features): Real-time 3D, motion with a reason and type with a voice, plus the parts most builders leave to you: sign-in, data, payments and your domain.
- [3D website builder](http://localhost:3000/features/3d-website-builder): Real-time 3D websites designed around your idea: what the 3D is for, how it is built from open-licence assets, how fast it loads on a slow phone, and when 3D is the wrong choice.
- [AI website builder](http://localhost:3000/features/ai-website-builder): What makes Laarpi different from a typical AI website builder: where it starts, what it asks, how it checks its own work, what it refuses to do, and how to write a prompt that gets a better site.
- [Animated websites](http://localhost:3000/features/animated-websites): Animated and interactive websites where each movement does a job: reveal, sequence, response or play. Laarpi's rules require a reduced-motion version that still works.
- [Website backend](http://localhost:3000/features/website-backend): What Laarpi sets up in your own Supabase project, how connecting works step by step, the access rules that protect each table, and what to do before real visitors sign in.
- [Website payments](http://localhost:3000/features/website-payments): What you can sell, how Laarpi turns products into working checkout on your own Polar account, why a merchant of record takes care of sales tax, and how to test before you sell.
- [Custom domains](http://localhost:3000/features/custom-domains): The DNS records to add, the difference between a bare domain and www, what each status means, and how to fix the snags that keep a domain from going live.
- [AI-ready websites](http://localhost:3000/features/ai-ready-websites): What an AI agent sees when it visits a Laarpi site, how it finds the agent door, why the door is compiled from the same source as the site instead of bolted on, and the readiness score that checks it.
- [Remix](http://localhost:3000/features/remix): How remixing a community site works, what carries over and what starts fresh, how to remix well instead of renaming someone else's work, and how to share your own site.
- [Vibe coding a website](http://localhost:3000/features/vibe-coding-websites): Vibe coding for websites: describe the idea, answer the few questions that matter, watch the site take shape, direct it in plain words, and publish it. What a session involves and what gets checked.
- [A website from your brand guidelines](http://localhost:3000/features/website-from-brand-guidelines): How SI is built to work from your brand guide and assets: logos placed as supplied, your colours, fonts and copy followed as rules, and nothing invented.

## Use cases

- [All use cases](http://localhost:3000/use-cases): A photographer needs the work to load fast. A launch needs one moment people remember. A brand needs to look like itself. Pick what you are building.
- [Portfolio websites](http://localhost:3000/use-cases/portfolio-website): What a portfolio website has to do in its first ten seconds, how to structure it, and how to give it a look that belongs to your practice instead of a template.
- [Photography portfolios](http://localhost:3000/use-cases/photography-portfolio): How to sequence, size, load and frame photographs on the web so the site serves the work, and how Laarpi builds a photography portfolio around your images.
- [Architecture portfolios](http://localhost:3000/use-cases/architecture-portfolio): What an architect's or practice's website needs, how to present drawings, photographs and models on the web, and when real-time 3D helps a project rather than decorating it.
- [Music artist websites](http://localhost:3000/use-cases/music-artist-website): What an artist, band or label website needs for fans, press and promoters, how to build a release page around one idea, and how Laarpi designs one from the music outward.
- [Event websites](http://localhost:3000/use-cases/event-website): How an event website changes from announcement to the day itself, what people need at each stage, and how Laarpi builds festival, exhibition and conference sites with an idea of their own.
- [Product launch pages](http://localhost:3000/use-cases/product-launch-page): Launch pages that make the product the hero: something visitors can turn, open or play, then a price, a date and one action, with waitlists wired in.
- [SaaS landing pages](http://localhost:3000/use-cases/saas-landing-page): Why most SaaS landing pages look identical, what to put in their place, and how Laarpi builds a software landing page with sign-in and subscription checkout on your own accounts.
- [Agency websites](http://localhost:3000/use-cases/agency-website): How a creative or digital agency's own website should be positioned and structured, why case studies matter more than services lists, and how studios use Laarpi for their own site and for client work.
- [Brand website](http://localhost:3000/use-cases/brand-website): Brand sites built from the brand's own material, with craft shown rather than described: what the site has to do, a dissected example, the sections and the type.
- [A startup website that shows the product](http://localhost:3000/use-cases/startup-website): Startup sites for teams launching something visual: the four readers, the sections, what this year's startup homepages are built with, and how to build one.

## Styles (design directions)

- [All styles (design directions)](http://localhost:3000/styles): A direction is a starting point for taste: palette, type, layout and motion that belong together. The agent picks one from your idea, or you do. The site is still designed from scratch.
- [Swiss Brutal](http://localhost:3000/styles/swiss-brutal): A style for architects, engineers and studios whose work is precise: the discipline of Swiss typography with the honesty of brutalism. What defines it, the palettes and type behind it, and how to avoid its clichés.
- [Editorial Luxe](http://localhost:3000/styles/editorial-luxe): A style for fashion houses, photographers and publishers who would rather be read than skimmed. What makes a site feel like a magazine spread, the type and palettes behind it, and where it goes wrong.
- [Kinetic Type](http://localhost:3000/styles/kinetic-type): A style for festivals, labels and studios with a strong name and few images, where the type does the work photography usually does. How it moves, what it is built from, and how to keep it readable.
- [Liquid Chrome](http://localhost:3000/styles/liquid-chrome): A style for product launches that want a tactile hero instead of a screenshot. How one real-time object carries the page, the palettes and type around it, and how to keep the shine from turning into a cliché.
- [Analog Warmth](http://localhost:3000/styles/analog-warmth): A style for bakeries, cafés, makers and family businesses with a story and a place. How to make a site feel printed and handled, the type and palettes behind it, and what to prepare.
- [Gallery White Cube](http://localhost:3000/styles/gallery-white-cube): A style for painters, photographers and galleries who want the work to do all the talking. How the white-wall approach works on screen, the type and palettes behind it, and how to prepare the hang.
- [Cinematic Noir](http://localhost:3000/styles/cinematic-noir): A style for cinemas, late-night places, releases and stories that happen after dark. How to make a site feel like a film, the grade and type behind it, and how to keep dark pages readable.
- [Retro-Futurist Terminal](http://localhost:3000/styles/retro-futurist-terminal): A style for science projects, developer tools and hardware whose facts are part of the appeal. How the console look works on screen, the phosphor and blueprint palettes, and the clichés to avoid.
- [Organic Biomorph](http://localhost:3000/styles/organic-biomorph): A style for skincare, botanical, ocean and life-science brands that should feel alive. How soft, living forms are built without crude stand-ins, the palettes and type behind them, and where the style goes wrong.
- [Acid Rave](http://localhost:3000/styles/acid-rave): A style for club nights, festivals and labels that should feel like a night out. How to get flyer energy on screen while keeping dates, lineups and tickets easy to find, and the safety rules for loud motion.
- [Botanical Archive](http://localhost:3000/styles/botanical-archive): A style for gardens, museums, perfumers and anyone with a collection to show. How the logic of plate, label and ledger becomes a website, the type and palettes behind it, and what to prepare.
- [Industrial Spec Sheet](http://localhost:3000/styles/industrial-spec-sheet): A style for hardware, tools, gear and manufacturers whose numbers are part of the pleasure. How to make a datasheet desirable, the type and palettes behind it, and how to write specs people read.
- [Playful Toybox](http://localhost:3000/styles/playful-toybox): A style for toy makers, kids' brands, snacks and anything that should make people grin. How to be playful without being childish, the type and palettes behind it, and how to serve both the player and the payer.
- [Quiet Luxury](http://localhost:3000/styles/quiet-luxury): A style for boutique hotels, small restaurants and makers of fine goods whose customers do not want to be shouted at. How restraint becomes a material, the details that signal quality, and what to avoid.
- [Riso Zine](http://localhost:3000/styles/riso-zine): A style for zine fairs, bookshops, small labels and community events. How risograph printing translates to the screen, why overprinting is the whole trick, and how to avoid a site that looks like a filter.
- [Dimensional Pop](http://localhost:3000/styles/dimensional-pop): A style for consumer product launches with one hero object and a sense of fun. How faux-3D type and a glossy real-time object share the page, the hot palettes behind it, and how to keep it focused.

## Comparisons and alternatives

- [All comparisons and alternatives](http://localhost:3000/compare): How Laarpi differs from the site builders and coding agents you may already use. Factual, dated and sourced.
- [Laarpi vs Framer](http://localhost:3000/compare/laarpi-vs-framer): A fair, dated comparison of Framer's design canvas and Laarpi's describe-and-direct agent, with sources for every Framer fact.
- [Laarpi vs Webflow](http://localhost:3000/compare/laarpi-vs-webflow): Webflow is a visual development platform with a CMS, ecommerce and GSAP-powered interactions, built for teams who build by hand. Laarpi is a coding agent that designs each site from scratch, with real-time 3D and a backend on your accounts.
- [Laarpi vs Wix](http://localhost:3000/compare/laarpi-vs-wix): Wix is a website and business platform with an AI builder, templates, bookings, stores and marketing tools, hosted on Wix. Laarpi is a coding agent that designs each site from scratch, with real-time 3D, plain code you can read and edit, and a backend on your accounts.
- [Laarpi vs Squarespace](http://localhost:3000/compare/laarpi-vs-squarespace): Squarespace is a hosted website platform with polished design, Blueprint AI, commerce, courses and invoicing. Laarpi is a coding agent that designs each site from scratch, with real-time 3D, plain code you can read and edit, and a backend on your accounts.
- [Laarpi vs Lovable](http://localhost:3000/compare/laarpi-vs-lovable): A fair, dated comparison of Lovable's app builder and Laarpi's website agent, with sources for every Lovable fact.
- [Laarpi vs Bolt](http://localhost:3000/compare/laarpi-vs-bolt): Bolt is a chat-based builder for apps, websites and prototypes, with Bolt Cloud for hosting and databases. Laarpi takes a website from a thought to a finished site in one place: designed from scratch, with real-time 3D, on your own Supabase and Polar.
- [Laarpi vs v0](http://localhost:3000/compare/laarpi-vs-v0): v0 by Vercel is an AI agent that builds Next.js apps and interfaces and deploys them to Vercel. Laarpi takes a website from a thought to a finished site in one place: designed from scratch, with real-time 3D, on your own Supabase and Polar.
- [Dora alternatives](http://localhost:3000/alternatives/dora-alternatives): Dora's verified status, and fair options for building 3D and animated sites now: what each tool does, what it costs and who it suits.

## Guides

- [All guides](http://localhost:3000/guides): Practical, specific and long enough to be useful: 3D on the web, type, motion, performance, and the pages that have to earn their keep.
- [How to build a 3D website](http://localhost:3000/guides/how-to-build-a-3d-website): Two honest paths to a 3D website, with real code, asset prep and performance numbers measured on our own sites.
- [WebGL for designers](http://localhost:3000/guides/webgl-for-designers): A designer's guide to WebGL and three.js: the mental model, the vocabulary, what each technique costs, and how to brief real-time 3D so it comes back the way you imagined.
- [A portfolio that gets you hired](http://localhost:3000/guides/portfolio-that-gets-you-hired): How portfolio reviewers actually read, what to show for each creative discipline, how to write case studies that prove your judgement, and how to make the site itself part of the argument.
- [A launch page that converts](http://localhost:3000/guides/product-launch-page-that-converts): How to plan, write and structure a product launch page around one action: positioning, the order of beats, headlines, calls to action, honest proof, waitlists and what to measure.
- [Choosing fonts that aren’t Inter](http://localhost:3000/guides/choosing-fonts-that-arent-inter): Why so many websites share the same handful of typefaces, how to choose display, text and label faces for a concept, sixteen tested pairings with reasons, and how to license and load them properly.
- [Fast websites with 3D](http://localhost:3000/guides/website-performance-with-3d): Measured load times for eight real-time 3D sites, where the time goes, and the fixes that cut it without changing a pixel.
- [Accessible motion](http://localhost:3000/guides/accessible-motion): Reduced-motion versions, flashing limits and keyboard paths for motion-heavy sites, shown on three real 3D and scroll sites with and without motion.
- [What is llms.txt](http://localhost:3000/guides/what-is-llms-txt): llms.txt is a map for AI agents, not a ranking signal. What the v2 proposal asks for, what the evidence says about who reads it, and how to make yours findable.
- [How AI agents read websites](http://localhost:3000/guides/how-ai-agents-read-websites): An AI system that visits your page is one of three readers, and each misses different things. What the vendors document about each one, and the same page captured all three ways.
- [Structured data for AI search](http://localhost:3000/guides/structured-data-for-ai-search): No special markup gets you into AI answers, and Google says so. What JSON-LD is documented to do, the one placement rule that decides whether AI crawlers see it, and two templates that validate.
- [robots.txt for AI crawlers, one bot at a time](http://localhost:3000/guides/robots-txt-for-ai-crawlers): AI crawlers do three different jobs, and each vendor names a separate token for each. A table built from the vendors' own pages, the RFC rules that trip people up, and three files to copy.
- [What is WebMCP, and should your site use it yet?](http://localhost:3000/guides/webmcp-for-site-owners): WebMCP turns a page's forms and functions into named tools that a browser agent can call, instead of guessing at buttons. What it is, where it really works as of October 2026, a form we tested in Chrome, and the rules that keep it safe.
- [Why ChatGPT, Claude or Perplexity can't see your website](http://localhost:3000/guides/why-ai-cant-see-your-website): When an assistant can't read your site, the cause is almost always one of five layers: robots.txt, your CDN, JavaScript, discovery or the assistant's own index. A test for each, in the vendors' own words.

## Examples

- [All examples](http://localhost:3000/examples): Each collection opens with the Laarpi team's own concept sites, explained and measured, then public sites worth studying, credited and linked.
- [3D website examples](http://localhost:3000/examples/3d-websites): Sixteen real-time 3D websites, eight of them ours with how-they-were-made notes and measured phone load times, eight public sites worth studying.
- [Interactive website examples](http://localhost:3000/examples/interactive-websites): Interactive and immersive sites sorted by what the visitor does (play, hold still, steer, stir), with notes on how each works with a mouse, a finger and a keyboard.

## Showcase sites

Made by the Laarpi team with Laarpi's library and process.

- [Aster & Kiln](http://localhost:3000/community/aster-kiln): Scroll throws a stoneware vase, then fires it to 1280 °C behind a kiln spyhole.
- [BASALT Tapes: Obsidian Hours](http://localhost:3000/community/basalt): An LP as a slab of obsidian: light it, turn it, break it into its eight hours.
- [FLUOR 26](http://localhost:3000/community/fluor): Three nights of electronic music in a disused power station, printed in ink you can stir.
- [HADAL](http://localhost:3000/community/hadal): Scroll to the floor of the Kermadec Trench. Below 1,000 m your cursor is the lamp.
- [Hortus Nocturne](http://localhost:3000/community/hortus-nocturne): A pressed gazania that stands up and blooms only while you hold the cursor still.
- [Meridian M-01](http://localhost:3000/community/meridian): A hand-wound calibre you can wind, take apart under a loupe and watch start again.
- [PATCH-01 by Ferro Instruments](http://localhost:3000/community/patch-01): A Eurorack voice you can play in the page: turn it, patch it, take it apart, hear it.
- [Salt & Smoke](http://localhost:3000/community/salt-smoke): One fire on an Oregon bluff, sunset to moonrise. Tonight's menu is written in its smoke.

## Optional

- [Full text of every page](http://localhost:3000/llms-full.txt): all features, use cases, styles, comparisons and guides in one file.