Motion, written as code
Motion graphics from a library of 174 runnable patterns
Kamply ships 174 motion patterns across 13 buckets, every one real Remotion source that plays in your own brand tokens. Open a pattern full page and you get a scrub bar and its recipe. A build gate fails any reel that spans fewer than 5 of those buckets.
Every reel has to span at least 5 of these 13 buckets.
The 174 patterns and their 13 buckets were counted on 2026-08-27 as folders in the shipped motion library, and the five-bucket rule is the span the reel gate checks.
What it actually does
Kamply is a Mac desktop app. Motion is written as React components driven by the frame number and rendered with Remotion, so the same composition at the same frame always produces the same pixels. Three things sit behind that: a library of 174 patterns you browse as live players and copy into your own reel, a shared physics layer of named curve families and spring presets, and a lint that reads the motion code with no render and fails the build on CSS keyframes or off-spec physics. You get an MP4 and every source file behind it.
What this is not
There is no prompt-to-video model here, no After Effects or Lottie import, and no drag-handle timeline to edit in. Motion is authored in code, you approve what it does, and you upload the finished file yourself.
How it runs, start to finish
Three steps, in the order the app actually does them.
Open the patterns view, copy a ref
The app's Patterns view lists the video library grouped by bucket, each tile playing its real composition in your brand tokens. Open one and it fills the pane with a scrub bar and the recipe beside it. Every card has a copy-ref button that puts the pattern's ref on the clipboard, camera/orbit-settle-3d for instance, and you paste that ref back to the AI to say build this one.
Author the score as a data file
The reel's choreography is written as a per-beat motion score: a data file that names a curve family and a spring preset from the shared physics layer, then compiles to frame-driven Remotion. The laws are shared across every reel, so the feel stays consistent. The choreography is written fresh for each one.
Lint, tune, then render once
A static lint reads the motion code with no render. CSS keyframes fail every reel. On a reel built on the shared physics layer it also fails an easing curve outside the brand families and a raw spring damping under the profile's floor, 170 on the default calm setting. A tune loop prints the per-channel jerk scorecard with no render at all, so you change a curve and watch the numbers move. The finished MP4 then gets a freeze check that fails any dead hold of 2 seconds or longer.
The numbers, and where they come from
Every figure on this page traces to a published source or to Kamply's own measurements. Nothing is modelled.
- Pattern library
- 174 patterns, 13 buckets
- Counted 2026-08-27 as folders in the shipped library; each holds a recipe and a matching runnable Remotion component. Every reel deposits a new lead pattern, so the count grows with use.
- Variety gate
- 5 buckets minimum per reel
- The same gate fails a lead pattern repeated inside 3 consecutive beats, and a lead pattern reused from another reel.
- Spring damping floor
- 170 on the calm profile
- From the shared motion registry the lint reads. On the default calm profile a raw damping under 170 fails the build, with one sanctioned exception: the badgePop spring at 18. A reel that opts into the launch profile lints against a floor of 18 instead.
- Overshoot budget
- 8 percent on the calm profile
- Budgets in the same registry. capStagger in the shared physics layer rescales a stagger spread to fit 20 frames; the 8 percent overshoot and the 15 percent anticipation ceiling are written into the pattern source by hand, not checked by a tool. The lint gates CSS animation, off-family curves and spring damping, not these.
- Dead-hold check
- 2.0 seconds
- Run on the rendered MP4 with a freeze detect tuned to ignore grain, after the render, not on the source.
- Art-direction styles
- 13 buildable now, of 16 specified
- Each buildable style has a rendered showcase reel; the other 3 need real footage supplied.
Questions people actually ask
If yours is not here, ask it in the walkthrough. The form below reaches a human.
Can I type a prompt and get a motion graphic out?
No. There is no generative video model anywhere in Kamply. Motion is authored as React components driven by the frame number and rendered headlessly, which is why the same composition at the same frame always gives the same pixels. What the AI writes is code you can read, re-render and hand to someone else.
Can I import an After Effects file, a Lottie JSON, or edit on a timeline?
None of those. The Lottie bridge was researched and declined, because importing an animation blob works against motion being written in code, and the Skia one was declined with it. There is no drag-handle editor either: the choreography is a data file you change, and the timeline in the app is read-only on purpose so the gates stay the only path to a render.
Is the 3D real, or faked perspective?
Real, through the official Remotion bridge to Three.js, with 14 patterns in the 3D bucket covering device rotates, extruded bars, parallax stacks, orbits, crane reveals and rack focus. Objects are built from code primitives, so there are no stock GLB models to license. A reel that touches 3D is switched to a software CPU renderer automatically, so the same frame looks the same on any machine; flat 2D reels stay on the GPU because they do not need it. Extruded 3D type and 3D logo stings are ruled out as too loud.
Does it actually measure whether the motion is smooth?
It does. A scorer computes normalized RMS jerk per animated channel, weighting position, scale and opacity at 0.5, 0.3 and 0.2, either from the score's sampled value curves or straight off the rendered frames. The number tells you which channel to look at. It never blocks a build, and you still judge the reel by watching it.
Can it animate my screen recording, or sharpen a small image?
It does not record your screen. The screen-capture style builds the interface in code instead. A real recording is footage you bring in, and it gets cut as an edited video against an edit list with a graded look and captions applied last. There is no upscaler either: stock is fetched at original resolution, because a 1300 pixel source in a 1080 by 1920 plate is already soft before any camera push.
What do I need to run it, and what does it cost?
An Apple silicon Mac on macOS 11 or later. Kamply ships as a signed, notarized DMG, with no web app and no mobile app. One plan: $69 a week, $199 a month or $1,990 a year, with an Enterprise lane that books a walkthrough. Founding rates end 2026-09-15. Nothing publishes, schedules or reports on performance: you get the file.
Bring one brief. Watch your first campaign take shape.
We build the first direction with your brand during the walkthrough. You leave knowing exactly what Kamply would make next.