# Table of Contents - [Account & Billing · Originkit](#account-billing-originkit) - [Why Originkit · Originkit](#why-originkit-originkit) - [Components · Originkit](#components-originkit) - [Templates · Originkit](#templates-originkit) - [Sections · Originkit](#sections-originkit) - [Privacy Policy · Originkit](#privacy-policy-originkit) - [Terms & Conditions · Originkit](#terms-conditions-originkit) - [Report a Bug · Originkit](#report-a-bug-originkit) - [Request a Feature · Originkit](#request-a-feature-originkit) - [Licensing & Usage · Originkit](#licensing-usage-originkit) - [Contact Support · Originkit](#contact-support-originkit) - [FAQ · Originkit](#faq-originkit) --- # Account & Billing · Originkit Account & Billing ================= Last updated: Wed 19 Aug 2026 This policy explains how refunds and cancellations work for paid Originkit plans. It forms part of our [Terms & Conditions](https://www.originkit.dev/docs/terms) . We've kept it plain. If something here doesn't cover your situation, write to [hello@lander.studio](mailto:hello@lander.studio) , and we'll sort it out. * * * 1\. Refund window ----------------- If a paid plan isn't right for you, request a refund within 7 days of your first payment, and we'll refund it in full. This applies to: * Your first subscription payment on a new account * Your first payment after upgrading to a higher tier To request one, email [hello@lander.studio](mailto:hello@lander.studio) from the address on your account with your order or invoice number. You don't need to justify the request. 2\. What isn't refundable ------------------------- * Renewal payments. Subscriptions renew automatically and renewals are non-refundable. Cancel before your renewal date to avoid the charge (see Section 4) * Requests made after 7 days from the initial payment * Accounts with substantial usage. Digital goods are delivered instantly and permanently. If an account has downloaded or exported an unusually large volume of components before requesting a refund, we may decline. This is a safeguard against abuse, not a trap for normal evaluation. Trying out a dozen components is exactly what the window is for * Accounts terminated for breach of our [Terms & Conditions](https://www.originkit.dev/docs/terms) or [Licensing & Usage](https://www.originkit.dev/docs/licensing) policy * Partnership and custom licensing fees, unless the agreement states otherwise 3\. Duplicate and accidental charges ------------------------------------ If you were charged twice, charged after cancelling, or charged in error, contact [hello@lander.studio](mailto:hello@lander.studio) and we will refund it in full regardless of the 7-day window. Billing mistakes are ours to fix. 4\. Cancelling a subscription ----------------------------- You can cancel at any time from your account billing settings, or by emailing [hello@lander.studio](mailto:hello@lander.studio) . When you cancel: * Your plan stays active until the end of the billing period you've already paid for * You keep full access to paid features until that date * You are not charged again * Cancellation is not prorated: we don't refund the unused part of a period, but you keep access for all of it After the period ends, your account reverts to the free tier. Your account, saved configurations, and presets remain intact. 5\. What happens to components you've already obtained ------------------------------------------------------ Components you legitimately obtained while subscribed remain licensed to you for projects already built, under the terms in our [Licensing & Usage](https://www.originkit.dev/docs/licensing) policy. Cancelling ends your access to download new premium components; it does not retroactively revoke rights to work you've already shipped. If a refund is issued, the license granted by that payment terminates. You must stop using premium components obtained under that subscription, except where they are already embedded in a project delivered to a client in good faith. 6\. Failed payments ------------------- If a payment fails, we'll retry and notify you. If it remains unpaid after 7 days, your account reverts to the free tier. You can restore access by updating your payment method. Your data is not deleted. 7\. How refunds are processed ----------------------------- Approved refunds are issued to the original payment method through our payment provider. * We respond to refund requests within 48hrs * Once approved, refunds are processed within 5-7 days * Your bank or card issuer may take additional time to reflect the credit, typically 5-10 business days Refunds are issued in the original currency of the transaction. We are not responsible for currency conversion differences or fees charged by your bank. 8\. Price changes ----------------- We may change pricing. Existing subscribers are notified in advance, and changes take effect from the next billing period. Price changes never apply retroactively to a period you've already paid for. If you don't want to continue at a new price, cancel before your renewal date. 9\. Taxes --------- Prices are exclusive of applicable taxes unless stated otherwise at checkout. Where GST or other taxes apply, they are shown before payment. Taxes already remitted to authorities may not be refundable in all cases. 10\. Discontinued service ------------------------- If we discontinue a paid plan or the service entirely, we will notify subscribers and refund the unused portion of any prepaid period on a prorated basis. 11\. Contact ------------ For any billing, refund, or cancellation question: Originkit Bengaluru, Karnataka, India [hello@lander.studio](mailto:hello@lander.studio) We answer billing emails quickly and we don't make refunds difficult. --- # Why Originkit · Originkit Why Originkit ============= Because the hard part was never finding a component; it was making it yours without breaking it. There is no shortage of component libraries. There are hundreds. What there is a shortage of is components you can drop into a real product, customize to a real brand, and ship on a real deadline, without spending three days fixing motion that jitters on mid-range hardware or a gradient that fights your design system. Originkit exists to remove that entire category of work. * * * Every component is built, not generated --------------------------------------- Each component in the library is hand-built and tuned before it ever appears in the catalog. Easing curves are chosen, not defaulted. Animations run on compositor-friendly properties, so they hold 60 fps on hardware people actually own. Shaders come with performance budgets. Reduced-motion preferences are respected. Keyboard and screen-reader behavior is handled. That work happens once, on our side. You inherit it for free, on every component, forever. The code is yours the moment you copy it ---------------------------------------- No package to install. No wrapper abstraction. No breaking change in v3 that forces a migration. You copy real React, Next.js, TypeScript, and Tailwind source into your project, and from that point it belongs to you, edit it, fork it, strip it, rename it. Libraries that ship as dependencies make you a tenant in someone else's codebase. OriginKit makes you the owner. Customization is a system, not a scavenger hunt ----------------------------------------------- Most libraries expose a handful of props and bury everything meaningful in the source. OriginKit exposes the real internals, colors, gradients, timing, easing, blur, shader uniforms, stagger, scroll offsets, and breakpoint behavior as structured, editable variables. And they're ordered identically across the entire library: Scene → Camera → Shape → Motion → Elements → Interaction. Learn the pattern once, and every future component will be familiar. That consistency is what turns a collection of components into a system. Two editors that get you to production -------------------------------------- The Variable Editor gives you a live preview and real controls. Adjust, watch it respond, and export the exact configuration you built. What you preview is what you ship. The AI editor lets you describe the change instead of hunting for it. "Slow the reveal." "Warmer palette." "Disable the shader on mobile." It operates inside the component's known parameter space, editing valid values rather than rewriting your component into something that no longer compiles. This is the difference between a library and a workflow. Most tools hand you a starting point. OriginKit takes you to the finish line. Machine-readable by design -------------------------- Originkit ships structured component metadata, typed property schemas, and a documented MCP server at [mcp.originkit.dev](https://mcp.originkit.dev/) . Point Claude, Cursor, or any MCP-compatible agent at it, and your AI can discover the right component, read its parameters, and configure it correctly on the first attempt. Free-form generation produces plausible code. Constrained recombination of vetted components produces shippable code. As more of the web gets built by agents, the libraries that expose themselves properly to those agents become infrastructure. One component, three surfaces ----------------------------- The same component works as copyable source in your codebase, as a native code component with real property controls on a visual canvas, and as a structured asset your AI agent can pull. Same quality, same behavior, same parameters, whichever way your team works. Design and engineering stop maintaining two divergent versions of the same thing. The short version ----------------- | | Typical library | OriginKit | | --- | --- | --- | | Ownership | Install a dependency. | Copy the source, own it. | | Customization | A few props | Fully structured variables, live preview | | Editing | Read the source. | Variable Editor + AI Editor | | Motion quality | Varies | Tuned, budgeted, reduced-motion aware | | AI access | Copy-paste from docs | Native MCP server | | Surfaces | One | Code, canvas, and agent | --- # Components · Originkit Components ========== A component is one interactive element: a hero, a navbar, a pricing table, a card, a form. It is the smallest thing you can take from Originkit, and the only catalogue that reaches every surface we support. Every entry is a running component rather than a snippet in a documentation page. You open it, it renders. You change its controls, the preview responds. Whatever you settle on is what gets written into your project, so there is no second round of adjusting after the paste. * * * Components, sections, or templates? ----------------------------------- All three deliver real source you own. They differ in how much of the page they cover, and in which surfaces can receive them. | | Covers | Framer | Code | MCP | CLI | | --- | --- | --- | --- | --- | --- | | Components | One element | Yes | Yes | Yes | Yes | | \[Sections\](/docs/sections) | A page band and its children | No | Yes | No | Yes | | \[Templates\](/docs/templates) | A whole project | No | Yes | No | Prompt | Reach for a component when you need one piece and already have a page to put it in. If you are building the band itself, a section saves you wiring the children together. Framer support is components only. Before you start ---------------- * An account, to take anything. Browsing, previewing, and tweaking are open and cost nothing. Copying and installing need you signed in. * Node, for the CLI. Only if you install rather than paste. Nothing to install globally: `npx` fetches it per run. * An API key, for MCP and scripts. Not for interactive use. `originkit login` signs the CLI in through your browser instead. Keys live in Settings → API Integration. Preview and tune before you take it ----------------------------------- This is the part worth not skipping. The controls on a component page are its real props, not a demo skin: colors, theme, counts, radii, timing, and copy. Change them and the preview re-renders as you type. 1. Open a component. It renders live, exactly as it will behave in your project. 2. Tune the controls. Work until it looks like it belongs in your product, not ours. 3. Check the viewports. Desktop, tablet, and mobile, before you commit to it. 4. Copy in the format your tool wants. Framer source, React code, a CLI command, or an AI prompt. Your tweak state travels with every copy format. What you preview is what ships. None of this costs anything. You can explore the whole catalogue and spend an hour on one component without touching your allowance: the counter moves when code is delivered, not while you are deciding. In Framer --------- Pasted code components usually fail in Framer for predictable reasons: a named export instead of a default, no property controls, CSS keyframe animation, or `window` touched during render. Every Originkit component is authored against a spec that rules those out, so it works on the first paste. 1. Tune the component, then click Copy to Framer. You are copying the Framer variant, with its property controls intact. 2. In Framer, go to Insert → Code → New Component. This creates a code component with placeholder source. 3. Select all and paste over the placeholder. Replace the file's entire contents, not just part of it. 4. Drag it onto the canvas. The property controls appear in the right-hand panel. The values you set on the website arrive as the component's defaults, and every one of them stays adjustable from Framer's sidebar. Designers get real controls rather than a black box they have to open the code to change. Sections and templates do not work in Framer. They are React and Next.js source. In React, Next.js, and Vite --------------------------- One authored file backs every stack. The website preview, the Framer canvas, and the code MCP delivers all render the same source, adapted on the way out rather than forked per framework. | Stack | What you get | | --- | --- | | \`framer\` | The source as authored, `addPropertyControls` included | | \`react\`, \`vite\` | A plain component, with the Framer imports and controls stripped | | \`nextjs\` | The react variant plus `"use client"` where the component needs it | You can paste from the component page, where the dependency list sits beside the code. Installing is usually less work. ### The add command npx originkit add hero-spotlight That writes the source into your components directory, installs the npm packages it needs, and rewrites the import alias to match your project. If you have never run `originkit init`, it uses sensible defaults rather than stopping to ask. Add more than one at a time by listing them: `npx originkit add hero-spotlight feature-card`. ### Flags for add | Flag | What it does | | --- | --- | | \`--\` | Install a catalogue preset such as `--dark` or `--basic`. Writes `ui/-.tsx`, so it sits beside the default install rather than replacing it. | | \`--\` | Install one of your own saved style instances, in the same form. | | \`--prompt\` | Mark the install as coming from an AI prompt, for attribution. The website's prompt text adds this for you. Still a real delivery, so it still counts. | | \`--no-deps\` | Write the files, skip the package install. | | \`--dry-run\` | Print what would be written and installed, change nothing. | | \`-o, --overwrite\` | Overwrite files that already exist. | | \`--path \` | Override the components directory. | | \`--auth \` | Authenticate with an API key instead of the browser session. For CI and scripts. | ### Presets and saved styles A preset is a named look we ship with a component. A saved style instance is one you built yourself in the editor and kept. Both install to their own filename, which means you can hold several looks of the same component side by side: npx originkit add hero-spotlight # ui/hero-spotlight.tsx npx originkit add hero-spotlight --dark # ui/hero-spotlight-dark.tsx Nothing is overwritten, so trying a second style is not a decision you have to undo. ### The rest of the CLI npx originkit login # sign in through the browser, no API key npx originkit logout # clear the stored session npx originkit init # write components.json: install dir, alias, TypeScript npx originkit list # --kind component|section|template, --category npx originkit search npx originkit remove npx originkit whoami # which credential would be used; costs no quota `remove` deletes the files it wrote and leaves the npm packages installed, since anything else in your project may have come to rely on them. In AI editors, over MCP ----------------------- Originkit runs a real MCP server, not a copy-for-AI button. Your assistant queries the catalogue directly and receives working source, so it stops guessing at animation code it has never seen. ### Connect your client Copy the hosted endpoint, then open your client below for the exact step or config it wants. Chat apps and builders sign in with Originkit and need no key. Code editors take an API key, which you can create right here — once you have one it is filled into every command below, so there is nothing to paste by hand. Hosted HTTP endpoint — connect once, no local install step https://mcp.originkit.dev/mcp ![](https://www.originkit.dev/_next/image?url=%2Fbrand%2Ficons%2Fclaude.png&w=128&q=75&dpl=dpl_5y9D1BVniFrefns7BgVEYQfYNFx8)Claude (Web, Desktop, or Mobile) Custom connector Copy the hosted endpoint above, paste it here, then sign in — no API key Customize → Connectors → + → Add custom connector. Paste the URL, then Connect and approve Originkit. Leave Advanced OAuth fields empty — Originkit handles auth automatically. ![](https://www.originkit.dev/_next/image?url=%2Fbrand%2Ficons%2Fclawde.png&w=128&q=75&dpl=dpl_5y9D1BVniFrefns7BgVEYQfYNFx8)Claude Code Terminal Run once in your terminal, then restart Claude Code claude mcp add originkit https://mcp.originkit.dev/mcp --transport http --header "Authorization: Bearer " --scope user ![](https://www.originkit.dev/_next/image?url=%2Fbrand%2Ficons%2Fchatgpt.webp&w=128&q=75&dpl=dpl_5y9D1BVniFrefns7BgVEYQfYNFx8)ChatGPT (Web, Desktop, or Mobile) Custom connector Copy the hosted endpoint above, paste it here, then sign in — no API key Settings → Connectors → enable Developer Mode, then Create. Paste the URL and choose OAuth. Enable the connector in the chat composer. Deep Research uses search + fetch. ![](https://www.originkit.dev/_next/image?url=%2Fbrand%2Ficons%2Fcodex.png&w=128&q=75&dpl=dpl_5y9D1BVniFrefns7BgVEYQfYNFx8)Codex Terminal Run once in your terminal, then restart Codex export ORIGINKIT_API_KEY= codex mcp add originkit --url https://mcp.originkit.dev/mcp --bearer-token-env-var ORIGINKIT_API_KEY ![](https://www.originkit.dev/_next/image?url=%2Fbrand%2Ficons%2Fcursor.png&w=128&q=75&dpl=dpl_5y9D1BVniFrefns7BgVEYQfYNFx8)Cursor (or any IDE) .cursor/mcp.json Settings → MCP — same JSON works in Claude Desktop and other editors { "mcpServers": { "originkit": { "url": "https://mcp.originkit.dev/mcp", "headers": { "Authorization": "Bearer " } } } } ![](https://www.originkit.dev/_next/image?url=%2Fbrand%2Ficons%2Fantigravity.png&w=128&q=75&dpl=dpl_5y9D1BVniFrefns7BgVEYQfYNFx8)Antigravity mcp.json Add it to your MCP settings JSON, then restart Antigravity { "mcpServers": { "originkit": { "url": "https://mcp.originkit.dev/mcp", "headers": { "Authorization": "Bearer " } } } } ![](https://www.originkit.dev/_next/image?url=%2Fbrand%2Ficons%2Femergent.webp&w=128&q=75&dpl=dpl_5y9D1BVniFrefns7BgVEYQfYNFx8)Emergent Custom connector Copy the hosted endpoint above, paste it here, then sign in — no API key Add MCP connector → paste the URL, then complete the Originkit sign-in. ![](https://www.originkit.dev/_next/image?url=%2Fbrand%2Ficons%2Flovable.webp&w=128&q=75&dpl=dpl_5y9D1BVniFrefns7BgVEYQfYNFx8)Lovable Custom connector Copy the hosted endpoint above, paste it here, then sign in — no API key Project settings → Integrations → MCP → Add server → paste the URL, then sign in. ![](https://www.originkit.dev/_next/image?url=%2Fbrand%2Ficons%2Fbolt.webp&w=128&q=75&dpl=dpl_5y9D1BVniFrefns7BgVEYQfYNFx8)Bolt Custom connector Copy the hosted endpoint above, paste it here, then sign in — no API key Settings → MCP / Integrations → Add server → paste the URL, then sign in. ![](https://www.originkit.dev/_next/image?url=%2Fbrand%2Ficons%2Fwindsurf.png&w=128&q=75&dpl=dpl_5y9D1BVniFrefns7BgVEYQfYNFx8)Windsurf ~/.codeium/windsurf/mcp\_config.json Settings → MCP, or drop it in mcp\_config.json — then restart Windsurf { "mcpServers": { "originkit": { "url": "https://mcp.originkit.dev/mcp", "headers": { "Authorization": "Bearer " } } } } Replace with your key for code editors. Sign in to fill it in automatically. Custom connectors only need the hosted endpoint above. Then open any component, tune it, and take Copy → AI prompt. The prompt carries your settings and your assistant calls MCP to deliver the file. ### What the server exposes | Tool | What it does | Counts against limits | | --- | --- | --- | | \`list\_components\` | The catalogue index, filterable by category | No | | \`get\_component\` | Source for a component, adapted to your stack, with optional tweak values | Yes | | \`search\` | Keyword search returning components with citation URLs | No | | \`fetch\` | One component by id, with Next.js-ready source | Yes | `get_component` takes `name` as its only required argument. `stack`, `styling`, `typescript`, `preset`, and `tweaks` are all optional. `search` and `fetch` exist as a pair because ChatGPT Deep Research requires them. There is no generation tool. The server delivers a curated catalogue accurately; it does not invent components. ### Two ways to use it Straight from the editor, when you know roughly what you want: Get the feature-card component from originkit for my React + Vite project Or tune it on the website first, then take Copy → AI prompt. The prompt carries your settings, so the assistant reproduces the thing you already approved: Using originkit MCP, get me the pricing-three-tier component, dark theme, accent #7C3AED, 3 tiers, badge enabled. Worth asking your assistant to read `package.json`, `tailwind.config.js`, and `tsconfig.json` before its first request. Once it knows your stack and styling it passes them automatically, and you stop repeating yourself. What counts against your limits ------------------------------- Components are free to every signed-in account, within a daily and a weekly cap. Both apply at once, and whichever you reach first is the one that stops you. | | Per day | Per week | | --- | --- | --- | | Components | 10 | 25 | Days are IST calendar days and weeks run Monday to Sunday, IST. Current usage and reset times are in Settings → Daily Limit. | Counts | Does not count | | --- | --- | | Copying code or Framer source | Browsing and searching | | \`get\_component\` and \`fetch\` over MCP | Previewing and tweaking | | \`originkit add\` | Copying a CLI command or an AI prompt | | | `list`, `search`, `whoami` | The rule underneath is simple: the counter moves when code lands in your project, not when you look at it or copy instructions about it. Hitting a limit costs you nothing you already have, and it tells you when it resets. When something goes wrong ------------------------- * The Framer paste shows an error. Make sure you replaced the placeholder file entirely. A leftover `export function` from the template will collide with the component's default export. * The CLI cannot authenticate. Run `npx originkit whoami` to see which credential it would use. It costs no quota. If it reports nothing, run `npx originkit login`. * add refuses to overwrite. That is deliberate. Pass `-o` to replace the file, or install under a preset name so both survive. * Your assistant cannot see the tools. Check the endpoint has the `/mcp` suffix, and for OAuth clients that the advanced client ID and secret are empty. A filled-in client ID is the usual cause. * You are out of allowance. Settings → Daily Limit shows the reset time. Anything you already own is unaffected: entitlements bypass limits entirely. Still stuck? [Contact support](https://www.originkit.dev/docs/contact) with the component name, your stack, and the exact error text. --- # Templates · Originkit Templates ========= A template is an entire project rather than a piece of one: every page, the assets, and the config, wired together and ready to run. Templates come as React and Next.js projects, or as static HTML and CSS. Some are free; the rest are one-time purchases with no subscription attached. * * * Before you start ---------------- Templates install through an AI prompt that runs the CLI on your behalf, which means one prerequisite you do not need for components or sections. * An API key. The assistant runs the CLI as you, so it needs a credential of its own. The flow prompts you to create one if you have none. Settings → API Integration. * An AI editor. Claude Code, Cursor, or Codex. The prompt is written to be pasted into one of them. * Node. The assistant runs `npx` on your machine, in the directory you point it at. The key is shown once and stored only as a hash. Copy it when it appears; we cannot show it to you again. Getting a template ------------------ 1. Click Get, or Buy now on a paid one. The price is on the button, so there is no checkout surprise. 2. Copy the AI prompt. It carries the template name and your credential requirement. 3. Paste it into your editor, in the folder you want the project. The assistant does the rest. From there the assistant runs the CLI, unpacks the extract, and starts a dev server for React and Next.js templates or serves the static ones. You end up with a project running locally rather than a zip you still have to figure out. Paying for one -------------- Paid templates are one-time purchases. There is no subscription, no expiry, and no repurchase to get a later version. Checkout is handled by Dodo Payments as merchant of record, which means Dodo is the legal seller, collects and remits the tax for your jurisdiction, and issues the receipt. Card details never reach us. Access is recorded as soon as payment clears and shows up under Templates → Owned. If a purchase has not appeared after a few minutes, [contact support](https://www.originkit.dev/docs/contact) with your payment email and order reference. Refund terms are in [Account & Billing](https://www.originkit.dev/docs/account-billing) . What ownership gets you ----------------------- * It is permanent. An owned template stays under Templates → Owned. Closing and reopening an account does not take it away. * Install it as often as you like. Any machine, any project, any time. * It bypasses delivery limits. Entitlements are not metered, so reinstalling something you own never costs allowance. What counts against your limits ------------------------------- | | Per day | Per week | | --- | --- | --- | | Templates | 3 | 7 | These apply to free templates. Anything you have bought is exempt: ownership bypasses the counters entirely, so the limits only ever govern what you are trying out. When something goes wrong ------------------------- * The assistant says it is not authorized. It has no API key, or an old one. Create a fresh key in Settings → API Integration and paste the prompt again. * The project landed in the wrong folder. The assistant works in whatever directory it is open in. Open the target folder first, then paste. * A purchase has not shown up. Reconciliation usually catches it within a few minutes. After that, [contact support](https://www.originkit.dev/docs/contact) with your payment email and order reference. * You wanted it in Framer. Templates are code projects. Framer support is [components](https://www.originkit.dev/docs/components) only. --- # Sections · Originkit Sections ======== A section is a whole page band: a hero with its own heading, media, and call to action, or a pricing block with its cards and toggle. It arrives with every child component it depends on. The point of a section is that you do not assemble it. Where taking a band apart into components would mean six installs and wiring them together, a section is one command and the tree resolves itself. Sections are code only: React and Next.js. They are not Framer components, and they are not served over MCP. * * * Before you start ---------------- * A React or Next.js project. Sections are composed source, so there is no Framer or static-HTML path for them. * Node, and an account. `npx` runs the CLI without a global install. Sign in with `npx originkit login`. * Tailwind. Sections are styled the same way components are. The section's page lists anything else it needs. Installing a section -------------------- npx originkit add One command does the whole job. It walks the section's dependency tree, deduplicates children that appear more than once, writes every file, installs the npm packages, and rewrites the import alias to match your project. Deduplication matters more than it sounds. A band that uses the same button in four places should not write that button four times, and it does not. The [flags for \`add\`](https://www.originkit.dev/docs/components#add-flags) all apply here, including `--dry-run` if you want to see the file list before anything is written. That is worth doing the first time, since a section touches more of your tree than a component does. Working from the website ------------------------ Sections render live, the same as components. The difference is the source view: because a section is several files, you browse it file by file rather than reading one block of code. From there you can copy the CLI command, or an AI prompt that runs it for you. Copying either is free. Only the install itself counts. After installing ---------------- Files land in your components directory under your own alias, so the imports read like the rest of your codebase rather than announcing where they came from. The code is yours from that moment: edit it, rename it, delete half of it. Nothing updates underneath you. There is no runtime package, so a section cannot change after you have installed it. Picking up a newer version is a deliberate re-add with `-o`. npx originkit remove That deletes the files the install wrote. The npm packages stay, because by then other parts of your project may depend on them. What counts against your limits ------------------------------- | | Per day | Per week | | --- | --- | --- | | Sections | 5 | 10 | Section counters are separate from component ones, so installing sections never eats into your component allowance. A section counts once when it installs, however many child files it writes. Browsing, previewing, reading the source, and copying the command are all free. When something goes wrong ------------------------- * The install overwrote a component you had edited. A section installs its children too, and one of them shared a name. Use `--dry-run` first to see the file list, and `--path` to write it somewhere separate. * Imports do not resolve after installing. The alias is taken from `components.json`. Run `npx originkit init` to set it explicitly if you never have. * You wanted it in Framer. Not possible: sections are React source. The [components catalogue](https://www.originkit.dev/docs/components) is the Framer-compatible one. * Your AI editor cannot find the section. Expected. MCP serves components only. Ask your assistant to run the CLI command instead. Anything else, [contact support](https://www.originkit.dev/docs/contact) with the section name and the CLI output. --- # Privacy Policy · Originkit Privacy Policy ============== Last updated: Wed 19 Aug 2026 This Privacy Policy explains how OriginKit collects, uses, and protects your information when you use the OriginKit website, component library, editors, documentation, and MCP server (together, the "Service"). We keep this short and specific on purpose. If something here is unclear, write to [hello@lander.studio](mailto:hello@lander.studio) . * * * 1\. Our approach ---------------- Originkit is a component library. We don't need much data to run one, so we don't collect much. We do not sell your personal information, and we do not share it with advertisers. 2\. Information we collect -------------------------- ### Information you give us * Account information: name, email address, and password (stored hashed, never in plain text) if you create an account * Profile information: optional details such as display name or avatar * Payment information: if you purchase a paid plan, payments are processed by our payment provider. We receive transaction records and billing metadata, but we do not store your full card number * Communications: messages you send us via email, support, or feedback forms * Content you submit: component configurations, saved presets, project names, and prompts you enter into the AI Editor ### Information collected automatically * Usage data: pages viewed, components previewed or copied, features used, and referring URLs * Device and technical data: browser type, operating system, screen size, language, and approximate location derived from IP address * Log data: IP address, request timestamps, and error information * Cookies and local storage: see [Section 7](https://www.originkit.dev/docs/privacy#cookies) ### Information from third parties If you sign in through a third-party provider such as Google, we receive basic profile information from that provider, typically your name, email address, and avatar. We do not receive your password. 3\. How we use your information ------------------------------- We use information to: * Provide, operate, and maintain the service * Create and manage your account * Process payments and send billing communications * Save your component configurations and preferences * Operate the AI Editor and other AI-assisted features * Understand which components and features are used, so we can improve the library * Detect, prevent, and investigate abuse, fraud, and security incidents * Enforce our [Terms & Conditions](https://www.originkit.dev/docs/terms) * Send service announcements, and (with your consent) product updates * Comply with legal obligations We do not use your personal information to train AI models. 4\. AI Editor and AI features ----------------------------- When you use the AI Editor, your prompt and the relevant component parameters are sent to our AI provider to generate a response. * We send only what is needed to produce the output, your prompt and the component's configuration * We do not send your account credentials or payment information * Our AI provider processes this data under its own terms and does not use it to train its models on our API tier * We may retain prompts for a limited period to debug, prevent abuse, and improve the feature If you don't want a piece of information processed this way, don't include it in a prompt. 5\. MCP server -------------- When an AI agent connects to [mcp.originkit.dev](https://mcp.originkit.dev/) , we log standard request data (the components requested, timestamps, and connection metadata) to operate the service, apply rate limits, and prevent abuse. If you connect via an authenticated session, requests are associated with your account. We do not receive the contents of your conversation with your AI assistant, only the requests that assistant makes to our server. 6\. Legal bases for processing (EEA/UK users) --------------------------------------------- Where GDPR applies, we process personal data on these bases: * Contract: to provide the Service you've asked for * Legitimate interests: to secure, improve, and analyze the Service * Consent: for optional marketing communications and non-essential cookies * Legal obligation: where the law requires it You may withdraw consent at any time; this does not affect processing already carried out. 7\. Cookies and similar technologies ------------------------------------ We use: * Essential cookies: authentication, security, and core functionality. These cannot be disabled * Preference storage: your theme, editor settings, and saved configurations, typically in local storage * Analytics: aggregate usage measurement You can control cookies through your browser settings. Blocking essential cookies may break parts of the Service. 8\. Sharing your information ---------------------------- We share personal information only with: * Service providers: who help us operate the Service (hosting, database, CDN, email delivery, analytics, payment processing, and AI providers), each bound by confidentiality and data protection obligations * Legal and safety recipients: where required by law, court order, or to protect our rights, users, or the public * Business transfers: if we're involved in a merger, acquisition, or sale of assets, your information may transfer as part of that transaction. We will notify you before your information becomes subject to a different privacy policy We do not sell or rent personal information. Current providers include: Vercel (hosting), Cloudflare (CDN/security), Supabase (database), Resend (email) 9\. International transfers --------------------------- We operate globally, and your information may be processed in countries other than your own (including the United States and India), where data protection laws may differ. Where required, we use appropriate safeguards such as Standard Contractual Clauses. 10\. Security ------------- We protect your information with encryption in transit (HTTPS/TLS), hashed password storage, access controls, and regular review of our infrastructure. No system is perfectly secure. If a breach affects your personal information, we will notify you and the relevant authorities as required by law. 11\. Your rights ---------------- Depending on where you live, you may have the right to: * Access the personal information we hold about you * Correct inaccurate or incomplete information * Delete your personal information * Export your data in a portable format * Object to or restrict certain processing * Withdraw consent for consent-based processing * Opt out of marketing communications at any time * Not be discriminated against for exercising these rights To exercise any of these, email [hello@lander.studio](mailto:hello@lander.studio) . We'll respond within the timeframe required by applicable law, typically 30 days. We may need to verify your identity first. Indian users: Under the Digital Personal Data Protection Act, 2023, you may also nominate another individual to exercise your rights in the event of death or incapacity, and you may raise grievances with our [contact below](https://www.originkit.dev/docs/privacy#contact) before approaching the Data Protection Board. EEA/UK users: You have the right to lodge a complaint with your local supervisory authority. 12\. Children's privacy ----------------------- The service is not directed to children under 13, and we do not knowingly collect personal information from them. If you believe a child has provided us with information, contact [hello@lander.studio](mailto:hello@lander.studio) and we will delete it. 13\. Do Not Track ----------------- We do not currently respond to browser Do Not Track signals, as no common standard has been established. 14\. Changes to this policy --------------------------- We may update this Privacy Policy. Material changes will be reflected in the "Last updated" date above and, where appropriate, announced on the Service or by email. Continued use after changes take effect constitutes acceptance. 15\. Contact ------------ For privacy questions, requests, or grievances: Originkit Bengaluru, Karnataka, India [hello@lander.studio](mailto:hello@lander.studio) --- # Terms & Conditions · Originkit Terms & Conditions ================== Last updated: Wed 19 Aug 2026 Welcome to Originkit. These Terms & Conditions ("Terms") govern your access to and use of the Originkit website, component library, editors, documentation, and MCP server (together, the "Service"), operated by Originkit. By accessing or using the Service, you agree to these Terms. If you do not agree, please do not use the service. * * * 1\. The Service --------------- Originkit provides a library of animated user interface components, along with tools to preview, customize, and export them, including the Variable Editor, the AI Editor, framework-specific exports, and the Originkit MCP server at [mcp.originkit.dev](https://mcp.originkit.dev/) . Components may be delivered as copyable source code, as components for visual builders, or as structured assets retrieved by AI agents through MCP. 2\. Eligibility --------------- You must be at least 13 years old to use the Service. If you use the Service on behalf of an organization, you represent that you have authority to bind that organization to these Terms. 3\. Accounts ------------ Some features may require an account. You are responsible for maintaining the confidentiality of your credentials and for all activity that occurs under your account. Notify us at [hello@lander.studio](mailto:hello@lander.studio) if you believe your account has been compromised. We may suspend or terminate accounts that violate these Terms. 4\. Your rights to the components --------------------------------- Your rights to use, modify, and distribute Originkit components are set out in our [Licensing & Usage](https://www.originkit.dev/docs/licensing) document, which forms part of these Terms. Please read it: it governs what you can build and ship. In summary, and subject to that document: you may use components in personal and commercial projects, modify them freely, and ship them as part of a larger product. You may not redistribute the component library, or a substantial portion of it, as a competing component library, template pack, or asset marketplace. 5\. Acceptable use ------------------ You agree not to: * Use the Service to build or distribute unlawful, infringing, harmful, or deceptive material * Scrape, bulk-download, or systematically extract the library outside the intended interfaces * Circumvent rate limits, access controls, authentication, or usage metering * Resell, sublicense, or repackage the Service or its catalog as your own offering * Reverse engineer the service except to the extent that the restriction is unenforceable by law * Interfere with, overload, or disrupt the service or its infrastructure * Use automated systems in a manner that degrades the service for other users 6\. AI Editor and AI-assisted features -------------------------------------- The AI Editor and related features produce output based on your input and the component's parameters. AI output may contain errors, and identical prompts may produce different results. You are responsible for reviewing and testing any AI-generated or AI-modified output before using it in production. We make no warranty as to the accuracy, suitability, or performance of AI output. We may impose usage limits on AI features and may change or discontinue them. 7\. MCP server -------------- The Originkit MCP server is provided to enable AI agents and compatible tools to access the component catalog. Access is subject to these Terms, the [Licensing & Usage](https://www.originkit.dev/docs/licensing) document, and any rate limits or authentication requirements we apply. Components retrieved through MCP carry the same license as components obtained through any other surface. You remain responsible for the output of any agent you operate or authorize. 8\. Free and paid plans ----------------------- Parts of the service are free. We may introduce paid plans, usage limits, or premium features at any time. If you purchase a paid plan, pricing, billing cycle, and refund terms will be presented at checkout and form part of these terms. Fees are exclusive of taxes unless stated otherwise. Unless required by law or stated at purchase, fees are non-refundable. We may change pricing with reasonable notice. Changes will not affect the current billing period already paid for. 9\. Third-party services ------------------------ The service may link to or integrate with third-party tools, frameworks, hosting providers, and AI platforms. We do not control those services and are not responsible for them. Your use of a third-party service is governed by its own terms. 10\. Intellectual property -------------------------- The service, including the website, branding, documentation, editors, MCP infrastructure, catalog structure, and the components themselves, is owned by OriginKit and protected by applicable intellectual property laws. Except for the rights expressly granted in the [Licensing & Usage](https://www.originkit.dev/docs/licensing) document, no rights are transferred to you. The Originkit name and logo may not be used without our prior written permission. 11\. Availability and changes ----------------------------- We aim to keep the service available but do not guarantee uninterrupted access. We may modify, suspend, add to, or discontinue any part of the Service, including individual components, at any time. Components may be updated, renamed, or removed from the catalog. Source code you have already copied into your own project remains yours and is unaffected by catalog changes. 12\. Disclaimer of warranties ----------------------------- The service is provided "as is" and "as available." To the maximum extent permitted by law, we disclaim all warranties, express or implied, including merchantability, fitness for a particular purpose, non-infringement, accuracy, and uninterrupted or error-free operation. You use the service and its output at your own risk. 13\. Limitation of liability ---------------------------- To the maximum extent permitted by law, OriginKit and its team will not be liable for any indirect, incidental, special, consequential, or punitive damages, or for any loss of profits, revenue, data, goodwill, or business opportunity, arising from or related to your use of the Service. Some jurisdictions do not allow certain limitations, so parts of this section may not apply to you. 14\. Indemnity -------------- You agree to indemnify and hold harmless OriginKit and its team from any claims, damages, liabilities, and expenses (including reasonable legal fees) arising from your use of the Service, Your Content, your projects, or your breach of these Terms. 15\. Termination ---------------- You may stop using the service at any time. We may suspend or terminate your access if you breach these Terms or if we discontinue the Service. License rights granted for components already legitimately obtained and incorporated into your projects survive termination, subject to the [Licensing & Usage](https://www.originkit.dev/docs/licensing) document. Sections 4, 10, 12, 13, 14, and 17 survive termination. 16\. Changes to these Terms --------------------------- We may update these terms from time to time. Material changes will be reflected in the "Last updated" date above and, where appropriate, announced on the Service. Continued use after changes take effect constitutes acceptance. 17\. Governing law and disputes ------------------------------- These terms are governed by the laws of India, without regard to conflict of law principles. You agree to the exclusive jurisdiction of the courts located in Bengaluru, Karnataka, India. 18\. General ------------ These Terms, together with the [Licensing & Usage](https://www.originkit.dev/docs/licensing) document and the [Privacy Policy](https://www.originkit.dev/docs/privacy) , constitute the entire agreement between you and us regarding the Service. If any provision is found unenforceable, the remaining provisions stay in effect. Our failure to enforce a provision is not a waiver of it. You may not assign these Terms without our written consent; we may assign them in connection with a merger, acquisition, or sale of assets. 19\. Contact ------------ Questions about these Terms: Originkit Bengaluru, Karnataka, India [hello@lander.studio](mailto:hello@lander.studio) --- # Report a Bug · Originkit Report a Bug ============ Something not working right? Let us know what happened so we can fix it. 0/200 Send Report --- # Request a Feature · Originkit Request a Feature ================= Missing something? Tell us what you would like to see and how it would help. 0/200 Send Feature Request --- # Licensing & Usage · Originkit Licensing & Usage ================= Last updated: Wed 19 Aug 2026 This document sets out what you can and cannot do with Originkit components. It forms part of our [Terms & Conditions](https://www.originkit.dev/docs/terms) . We've written it in plain language on purpose. The short version: build and ship your own projects with the components freely. If you want to sell or distribute something that contains our components, partner with us. * * * 1\. The license --------------- When you obtain a component from Originkit (by copying its source, exporting from an editor, using it in a visual builder, or retrieving it through our MCP server), OriginKit grants you a worldwide, non-exclusive, royalty-free, perpetual license to use, modify, and incorporate that component into your own projects, subject to the restrictions in [Section 4](https://www.originkit.dev/docs/licensing#what-you-cannot-do) . This license is granted to you or to the organization you obtained the component on behalf of. It covers projects you build and operate. It does not cover products where the component itself is what's being distributed or sold. 2\. What you can do ------------------- * Use components in commercial work. Client projects, SaaS products, marketing sites, apps, internal tools, and the products you sell. * Use them in unlimited projects. There is no per-project, per-site, or per-seat limit. * Modify them however you want. Edit, extend, strip, restyle, refactor, rename, or rebuild. Once the source is in your project, it's yours to change. * Use them in client work. Agencies and freelancers may use components in websites and applications delivered to clients. The client may continue using and modifying the component as part of that delivered work. * Use them in open-source applications. You may include modified components in an open-source codebase, provided the project is a real application or site rather than a redistribution of our catalog. * Use them for teaching and learning. Study the code, use it in tutorials and courses, and reference it in articles. * No attribution required. Credit is welcome and appreciated, but it is never a condition of use. 3\. AI and MCP usage -------------------- Components retrieved through the Originkit MCP server carry exactly the same license as components obtained any other way. You may: * Connect AI agents and tools to our MCP server for your own development work * Ship applications that an AI agent assembled from Originkit components * Use components generated or modified via the AI Editor in commercial projects You may not: * Use MCP access to systematically mirror, cache, or replicate the catalog for redistribution * Expose our catalog through your own API, service, product, or agent as if it were yours * Use our components as training data for a model intended to generate a competing component library 4\. What you cannot do ---------------------- * Do not include components in templates, themes, or starter kits. You may not distribute or sell website templates, themes, boilerplates, or starter projects that contain Originkit components, whether free or paid, and whether the components are modified or not. * Do not distribute components as design assets. You may not sell or distribute design files, UI kits, Figma files, or design resources that reproduce Originkit components or their visual design. * Do not redistribute the library. You may not republish Originkit components, individually or in bulk, as a component library, UI kit, snippet collection, or asset marketplace. * Do not resell components as components. Selling a website you built with Originkit is fine. Selling an Originkit component, repackaged or lightly modified, as a product in its own right is not. * Do not build a competing catalog. You may not use our components, structure, metadata, or catalog as the basis for a competing component library or marketplace. * Do not claim authorship of the library. You may say you built your site with Originkit. You may not present the Originkit catalog as your own work. * Do not use our brand without permission. The Originkit name, logo, and visual identity are ours. Referring to us factually is fine; implying endorsement or partnership is not. * Do not use components in unlawful or harmful projects. Including anything unlawful, deceptive, infringing, or designed to harm others. 5\. The line, in one sentence ----------------------------- Build and run things with Originkit, as much as you like. If your customers receive the component rather than the result, you need a partnership. The test is simple: if the person paying you ends up with a reusable copy of our component (as a template, a design file, a starter kit, or an asset), that's distribution, not use. Talk to us first. If you're unsure which side you're on, ask at [hello@lander.studio](mailto:hello@lander.studio) . We'd rather answer than argue later. 6\. Partnerships ---------------- We work with template creators, design studios, agencies, and marketplaces who want to build products that include Originkit components. This is a real program, not a polite refusal. Partnerships can cover: * Templates and themes you sell on Framer, Webflow, marketplaces, or your own store * Design files and UI kits that reproduce our components * Starter kits and boilerplates distributed to other developers * Bundled or white-label use inside a product you're building * Marketplace listings and co-distribution arrangements Tell us what you're building and how you plan to distribute it, and we'll come back with terms. Approval is typically fast, and licensing terms are reasonable: we'd much rather have you build on us officially than not at all. Partnership enquiries: [hello@lander.studio](mailto:hello@lander.studio) 7\. Common scenarios -------------------- | Scenario | Allowed? | | --- | --- | | Client website using 12 Originkit components | Yes. | | Your SaaS product's marketing site and dashboard | Yes. | | An internal design system that includes modified components | Yes. | | An open-source portfolio site with a modified component | Yes. | | Teaching a course that uses Originkit components in examples | Yes. | | A paid template that includes our components | Partnership required | | A Figma or design file reproducing our components | Partnership required | | A starter kit or boilerplate distributed to other developers | Partnership required | | Selling your internal design system as a product to other companies | Partnership required | | A "500 animated components" pack containing our components | No | | A GitHub repo republishing the Originkit catalog | No | | A competing component marketplace seeded with our components | No | 8\. Third-party dependencies ---------------------------- Some components depend on third-party libraries, for example animation, 3D, or utility libraries. Those dependencies carry their own licenses, listed on each component's page. This license covers our code, not theirs. You are responsible for complying with third-party terms. Fonts, images, and icons used in previews are for demonstration only and may carry separate licenses. They are not covered by this license. 9\. Ownership ------------- This license grants permission to use, not ownership. OriginKit retains all rights, title, and interest in the OriginKit library, catalog, component designs, editors, documentation, MCP infrastructure, and brand. Modifications you make to a component are yours. The underlying component and its design remain ours. 10\. Paid plans and premium components -------------------------------------- If we introduce paid plans or premium components, additional terms may apply and will be presented at purchase. Unless stated otherwise, premium components carry the same usage rights and the same restrictions as free ones, including the restrictions on templates and design distribution. Rights to premium components obtained during an active subscription survive cancellation for projects already built. Access to download new components ends with the subscription. 11\. Perpetual rights --------------------- Once you have legitimately obtained a component, your license to use it in that project is perpetual. Later changes to this document, to our pricing, or to the catalog do not revoke rights to components you already hold. We may update this document for components obtained after the update takes effect. 12\. Termination ---------------- This license terminates automatically if you materially breach it. On termination, you must stop using and distributing the components, except where the component is embedded in a project already delivered to a client in good faith. We may pursue any remedy available at law for violations, particularly redistribution and unlicensed template or design distribution. 13\. No warranty ---------------- Components are provided "as is," without warranty of any kind. See [Section 12 of our Terms & Conditions](https://www.originkit.dev/docs/terms#warranties) for the full disclaimer and liability limitation. You are responsible for testing components before shipping them. 14\. Questions and permissions ------------------------------ If your use case isn't covered here, ask. We grant custom licenses and exceptions more often than you'd expect. Originkit Bengaluru, Karnataka, India [hello@lander.studio](mailto:hello@lander.studio) --- # Contact Support · Originkit Contact Support =============== Can't find what you're looking for? Get help from the OriginKit team. 0/200 Send Message --- # FAQ · Originkit FAQ === The questions we are asked most, answered as briefly as they deserve. What is Originkit? How long does it take to get the first component running? Which frameworks are supported? Is this a package I install? Can I modify the components? Do the components work on mobile? Will components break if you update them? What is the Variable Editor? What is the AI editor? Does what I preview match what I ship? What is the MCP server? How do I connect MCP? Can my AI see my private data through MCP? Can I use it commercially? What can't I do? Can I use it in a client project? How often are new components added? Still have questions? Can't find what you're looking for? Our support team is here to help. [Contact Support](https://www.originkit.dev/docs/contact) ---