[{"data":1,"prerenderedAt":88},["ShallowReactive",2],{"journal-why-vantra-design-exists":3},{"id":4,"title":5,"author":6,"body":9,"dateModified":75,"datePublished":76,"description":77,"extension":78,"lede":79,"meta":82,"navigation":83,"path":84,"seo":85,"stem":86,"__hash__":87},"journal\u002Fjournal\u002Fwhy-vantra-design-exists.md","Why Vantra.design exists",{"name":7,"role":8},"Kai Kauper","Design systems lead",{"type":10,"value":11,"toc":67},"minimark",[12,17,21,30,33,37,40,43,47,50,53,57,64],[13,14,16],"h2",{"id":15},"what-problem-does-vantra-solve","What problem does Vantra solve?",[18,19,20],"p",{},"Design system tooling today falls into two traps. The first is generality: directories and platforms that list everything and help with nothing in particular. The second is isolation: each tool knows one part of your system and nothing about the rest. A contrast checker knows your colours but not your components. A component linter knows your components but not who depends on them. An audit tool knows what is wrong but cannot tell you who breaks if you fix it.",[18,22,23,24,29],{},"Vantra starts from the opposite end. One shared library — ",[25,26,28],"a",{"href":27},"\u002Fhow-it-works","Vantra Core"," — reads the tokens and the component graph from your actual repository, and everything else is a question asked of that reading. A deprecation tracker, a design reviewer, an accessibility fixer: different instruments, one shared understanding of what your system contains.",[18,31,32],{},"The gap this fills is not discovery but action. Knowing that you have four buttons named Button is the easy half. Knowing who breaks if you remove three of them is the hard half, and that is the half most tooling skips.",[13,34,36],{"id":35},"why-local-first","Why local-first?",[18,38,39],{},"A contrast checker reads every colour on your page. A design reviewer reads your component source. An accessibility fixer reads the rendered DOM of your staging environment. These are exactly the kinds of access that should never be paired with a network request.",[18,41,42],{},"Local-first is not a marketing feature — it is a constraint that follows from what the tools do. Every Vantra tool runs on your machine or in your browser. There is no account, no upload, no telemetry, and no server to trust. That is also why they work behind a VPN, on a staging build, on a page you cannot share with a third party.",[13,44,46],{"id":45},"why-open-source","Why open source?",[18,48,49],{},"Governance tooling you cannot inspect is just an opinion with a process around it. If a tool claims to measure whether your design system follows its own rules, you should be able to read how the measurement works.",[18,51,52],{},"Every Vantra tool is published under an open-source licence. The repositories are public from the start — including the parts that are not finished, including the decisions that turned out to be wrong. That openness is not incidental. It is how the tools earn the kind of trust they ask for.",[13,54,56],{"id":55},"who-is-behind-vantra","Who is behind Vantra?",[18,58,59,60,63],{},"One person — ",[25,61,7],{"href":62},"\u002Fabout",", working independently from Böblingen, Germany. There is no team, no investors, and no roadmap written for a board. The pace is set by what can be done carefully rather than what would make a good slide.",[18,65,66],{},"That honesty is itself a positioning choice. Design system teams are used to tools that appear fully formed and then pivot, stall, or raise prices. Vantra trades that for something smaller and more verifiable: everything is on GitHub, the commit history is the track record, and the parts that are not ready say so on the box.",{"title":68,"searchDepth":69,"depth":69,"links":70},"",2,[71,72,73,74],{"id":15,"depth":69,"text":16},{"id":35,"depth":69,"text":36},{"id":45,"depth":69,"text":46},{"id":55,"depth":69,"text":56},null,"2026-08-14","Vantra builds local-first, open-source tools for the unglamorous parts of design systems. This is why it exists and what makes it different.","md",[80,81],"Vantra is a set of local-first, open-source tools for the parts of design systems nobody photographs — contrast ratios, deprecation timelines, component drift, the accessible name of a button. It exists because practical, specific tooling for people doing real design systems work is surprisingly hard to find.","This is not a funded startup or a tool directory. It is an independent project, built by one person, published openly because a tool about accountability should be accountable first.",{},true,"\u002Fjournal\u002Fwhy-vantra-design-exists",{"title":5,"description":77},"journal\u002Fwhy-vantra-design-exists","5pqOOJjTFkpucliI_tMj_bca516IAQDJ4T5CxeqOdiE",1786959446818]