VEED vs Lucide
Side-by-side trajectory, velocity, and editorial themes.
VEED has gone all-in on AI video and is now selling it as an API.
VEED's last six months tell a clear story: launch in-house Fabric 1.0 generative model, integrate Kling O1 for prompt-based video editing, retire the standalone AI Agent in favor of editor-native tools, and expose the whole stack as an API consumable from n8n. The editor has moved from manual cuts to AI-first generation and editing primitives. Public release notes have gone quiet since the n8n launch in late January.
VEED is repositioning from a browser editor to an AI video infrastructure layer that other workflows call into. The retirement of AI Agent in favor of in-editor tools is the consolidation step before opening the API, since fewer competing surfaces simplify the developer story. Expect more emphasis on programmatic and embedded use rather than human-in-the-editor workflows.
The next directional move is likely a more formal developer offering: standalone API docs, pricing tiers for batch generation, and additional integration targets beyond n8n (Zapier, Make, or direct SDKs). On the model side, an upgraded Fabric or Kling tier seems imminent.
Lucide is in a steady icon-addition cadence — eight minor releases in six weeks, mostly community PRs.
Lucide is releasing roughly twice a week along the 1.x line, with each minor adding 1–6 community-contributed icons (blender, broccoli, sticky note variants, repeat-off, waves-vertical, folder-bookmark, astroid, heart-x, layers-minus, bell-check) and refining existing ones (text-cursor, landmark, candy-cane, volleyball). Framework adapters (Svelte, Vue, Angular, React) receive small fixes alongside. There is no structural work in this window — it is a contributor-flow optimization.
The project sits in healthy steady-state. Low-friction PR throughput, regular minor versions, and no large refactors suggest Lucide has settled into being the default fork-and-extend icon library for designers and the maintainers are protecting that contributor pipeline rather than pushing a roadmap. Framework adapter parity is being maintained in lockstep with the core icon set.
Expect another 1–2 icons (or refinement PRs) per minor over the next few weeks, plus a framework-adapter patch as upstream Svelte/Vite/Vue dependencies shift. No 2.0 cut is signaled in this window.
See more alternatives to VEED →
See more alternatives to Lucide →