Stackness

Stackness is a social platform where people in IT show the tools, workflows, and approaches they use to get things built. It is built for everyone in IT with opinions about their setup, from engineers and designers to data folks and everyone in between. The main purpose is to give your setup a social home: you build a stack profile that you share as one link, post the moves behind that stack, follow people whose taste you trust, and discover what works. Most people working in tech have strong opinions about the tools they use, but there is rarely a good place to put that knowledge. Tools are what you install, while moves are how you actually work — the habits, rituals and workflow tricks that make a stack yours. Stackness exists to capture both. Rather than leaving your setup buried in a forgotten README or a chat thread, it turns it into a public, living profile. The platform also tracks how tools rise and fall over time, so the community can see which choices are gaining traction and which are slipping, instead of relying on isolated opinions. The first thing Stackness gives you is a profile you can customize to make it unique. You drag tiles where they belong, size up the ones that matter, tuck the little utilities into a cluster, and colour each subspace to taste, so that one link ends up looking like you. Tools are grouped into logical buckets. In the example shown on the site, a profile has a "Daily drivers" group holding nine tools and one move, listing Visual Studio Code, Tailwind CSS and Claude Code, plus a "Toolbelt" group with Next.js and Docker and another Toolbelt cluster of five items including Warp, Raycast, Postman, HTTPie and jq. Each tool can carry a personal note — for instance, "My daily driver for years" or "The TypeScript support is unbeatable" — giving context to why a tool earned its place rather than just naming it. Alongside tools, Stackness lets you show your moves. Moves are the switches, setups, and workflow tricks behind your stack; they share how you actually work rather than just what you installed. A move is written up with a title, a description, and the tools it involves. The example on the site is a prompt-driven TDD workflow: "I write the test prompt first, then implement until it runs green." Its steps are laid out in order — write a failing Vitest spec for the bug first and do not touch src/ until it runs red, let Claude Code scaffold the specs, run the suite so it must fail first, then implement until green. Moves like this make a stack legible to other people and give them something concrete they can copy. Discovery is the other half of the product. You can see what everyone else is using through trending tools, trending moves, and rising stars. Following is central to the experience: follow people whose taste you trust and keep an eye on the rest. Stackness surfaces a Top members list, with profile cards showing a member's handle, how many moves and tools they have listed, and a follow button, so you can build a feed of setups you find credible. Because everything is public and comparable, the platform doubles as a way to benchmark your own choices against people doing similar work. Every tool has its own page. A tool page shows popularity over twelve weeks, who else is using it, and what they keep it next to. The Tailwind CSS page, for example, is labelled a utility-first CSS framework for rapid UI development, filed under Languages & Frameworks, and shows usage on Stackness by week — starting at 128 members, then 131 members (up 3 in the last 12 weeks), then 126 members (down 2 in the last 12 weeks). This makes it possible to watch a tool climb the ranks or slip down them, and to see the company a tool keeps in real stacks. Stackness also publishes a blog with updates, announcements, trends and explainers. Posts are tagged for browsing — product-hunt, stacks, moves, changelog, trends, workflows and getting-started — and include an announcement that Stackness is live on Product Hunt, a changelog covering public trending pages, category hubs, move cards for your README, tile quick look and a nicer blog, plus a knowledge post answering "What is a move, anyway?". The blog is where the platform explains its concepts and shares its changes in public. Overall, Stackness works by turning a personal setup into structured, shareable content. You register, add the tools you use, arrange them into tiles and clusters, and attach notes explaining each choice. You then write moves that describe the switches, setups and workflow tricks behind your stack, linking the tools involved. Everything rolls up into a single profile link you can share anywhere. From there, the platform aggregates that data across members into trending tools, rising stars, and per-tool pages with twelve-week popularity charts, while the follow graph lets you curate whose stacks you watch. The benefits follow directly from that structure. Your stack becomes one link instead of a scattered list, so it is easy to share in a bio, a README, or a conversation. Notes and moves explain the reasoning behind your choices, which turns a tool list into something other people can actually learn from. Following people whose taste you trust gives you a filtered signal on what works, while tool pages and trend charts show whether a tool is gaining or losing momentum before you commit to it. And because the product is free to use, the barrier to showing your stack is essentially zero. Concrete use cases appear throughout the site. A developer builds a stack profile and shares it as one link with their team or audience. Someone writes up a prompt-driven TDD workflow as a move so colleagues can reproduce it step by step. A person deciding between similar libraries checks the relevant tool page to see popularity over twelve weeks and which other tools it is kept next to. Someone follows a handful of members whose setups they admire and watches the trending pages for rising stars. A vibe coder or an engineer documents daily drivers such as Visual Studio Code, Tailwind CSS and Claude Code, with a note explaining why each one stays. Stackness is for everyone in IT who has opinions about their setup: engineers, designers, data folks, and everyone in between, including developers and vibe coders. Joining is free, and the platform also offers an MCP server. Beyond that, an optional supporter tier costs CHF 5 per month and adds a weekly trends newsletter, trend waves with historical popularity charts, subscribers-only stacks and moves, a supporter badge on your profile, and early access to new features. A separate team option lets you back Stackness together with your whole team, with team perks described as just getting started. Stackness takes the tools and habits that usually live in your head and turns them into a public, browsable profile: build your stack, post your moves, follow trusted people, and watch tools rise and fall. It is a social home for your dev tools, and it is free to join.