Kobra vs Aceternity UI

Aceternity UI is the library behind a lot of the glowing, tilting, sparkling landing pages you've seen in the last few years. Background beams, spotlights, 3D cards, animated bento grids, text that types itself in. It's built with Next.js, Tailwind CSS and Motion, it has a large free collection, and its paid All-Access tier adds 200+ blocks and 15+ templates for $199 once.

Kobra is 100+ components on Base UI for the inside of an application: tables, comboboxes, command menus, toasts, sidebars and the agent interfaces that sit behind a login. Also $199 once.

So the headline price is identical and the libraries barely overlap. The useful question is which surface you're building, and how much of it should move.

How Kobra and Aceternity UI compare

What each one is for

Aceternity's free components include a signup form, a file upload and an animated modal, so it isn't purely decorative. But it has no data table, no combobox, no command menu, and its paid blocks are hero sections, pricing, testimonials, navbars, footers and the like. Kobra has no hero section, no testimonial wall and no templates. On the catalog alone, the choice comes down to which half of the product you're working on.

Motion, and what it's for

Both libraries are built around motion, and the difference in how they use it is the most useful thing on this page.

An effect somebody meets once can afford to be spectacular. An effect they trigger two hundred times a day has to be nearly invisible. Aceternity's effects are built for the first case and Kobra's for the second, and neither would survive being swapped.

How you install it

Where Kobra goes deeper

The components an application is made of

Forms with validation states, comboboxes with multi-select and typeahead, command menus, sidebars that resize and collapse, toasts that stack and swipe, OTP inputs, resizable panels, CRM and grouped tables, date pickers in several calendar systems. This is the part of a product people spend their working day in, and Aceternity doesn't cover it.

Accessibility as a foundation

Every interactive Kobra component sits on Base UI, which handles focus traps, roving tabindex, typeahead and screen reader semantics, and the library is tested against WCAG 2.1 AA in both themes. On a dashboard, people navigate by keyboard, and a dialog whose focus trap fails is one they can't leave. Aceternity's site doesn't describe a headless primitive layer or make accessibility claims, which matters much less on a hero section than on a settings page.

Agent interfaces

A chat input, messages, chat history, reasoning steps, a trace waterfall, a task list, plan and question cards, streaming text, inline citations, and generative UI such as an agent map, product cards and image generation. If you're building an AI product, this is the half of it users actually sit in.

A Figma kit, and right to left

Kobra publishes 52 primitives in Figma on the same tokens as the code, free on the Figma Community. And every component is written by reading direction, so under dir="rtl" the spacing, arrows, carousels and arrow keys all turn around. Aceternity's site mentions neither.

Buying one component

$19 buys a single Kobra component, and ten purchases are credited in full toward the library. Aceternity's free tier is generous, but its paid content comes as All-Access or not at all.

Where Aceternity UI goes deeper

A large free collection

100+ free components, with source, no account and no license. Kobra's free tier is 11 components. If your budget is zero and you want effects, Aceternity gives you far more to work with.

Effects people remember

Background beams, spotlights, sparkles, 3D cards, parallax scroll, animated text, cursor effects, shaders. Being memorable is the job on a landing page, and Aceternity's effects are built to be looked at. Kobra's motion is deliberately the opposite.

Marketing blocks and full templates

Hero sections, feature sections, logo clouds, bento grids, pricing, testimonials, CTAs, FAQs, navbars, footers and login pages, plus complete templates for agencies, studios and SaaS products. Kobra ships no templates and no marketing sections. If you need a site online this week, that settles it.

Licensing for client work

Aceternity's license lets you build unlimited end products for yourself or your clients, which suits agencies and freelancers who ship many marketing sites. Kobra's license covers commercial use too, but its catalog is aimed at one long-lived application rather than many short-lived sites.

What they cost

Aceternity lists its paid tiers as discounts from $299, $249 and $1,990. At the individual level the price is identical, and for ten developers the two land within $100 of each other, so price shouldn't decide this. What you're building should.

Prices read from the vendor's own pricing page on 30 October 2026.

Should you use both?

Yes. This is one of the clearest "both" cases on this site. The catalogs don't overlap, both install through the shadcn CLI as plain Tailwind source, and both use Motion, so there's no second animation library to reconcile. The usual arrangement is Aceternity for the marketing site and Kobra for the application, sharing one set of Tailwind tokens so the two halves look like one product.

Two things to watch. Both bring their own Button and modal, so pick one of each. And keep the motion where it belongs. A spotlight sweeping behind a settings form is as wrong as a hero section that doesn't move.

When to choose Kobra or Aceternity UI

These two cover opposite halves of the same product, at the same individual price, on the same one-time terms. The only wrong answer is picking one and asking it to do the other one's job.