Frequently Asked
Questions
Everything you need to know about Contra Collective Agency, our developer tools and open-source projects, our enterprise engineering work, and how the two sides of the studio fit together.
About Contra Collective
Contra Collective is an AI-first engineering agency headquartered in Los Angeles, California. The studio has two connected sides: an enterprise practice at contracollective.com that architects autonomous multi-agent systems, agentic workflows, and AI-embedded commerce for brands on Shopify Plus, Salesforce Commerce Cloud (SFCC), and custom stacks — and a product lab at contracollective.dev that ships the developer tools, CLIs, and open-source infrastructure built during agency delivery. Every tool on the product-lab side (Contra Swarm, Switchboard, Linear CLI, ShellShade, GChat CLI, Shopify Monitor) was forged inside a real client engagement before being extracted, hardened, and open-sourced. You are looking at the developer-facing half of the same company.
Both, by design. The enterprise practice at contracollective.com delivers custom agentic systems and AI engineering for Fortune 500 and high-growth brands. The product lab at contracollective.dev maintains the open-source toolchain the agency uses internally — released publicly because we want clients to self-host, audit, and extend the systems they depend on. This structure is deliberate. Tools that survive agency delivery are the only ones we open-source. Tools that stay internal usually die when the client engagement that birthed them ends.
Contra Collective Agency is based in Los Angeles, California (90292). The team is distributed across North America but the studio's registered address and operations center are in LA. Enterprise engagement calls are scheduled in Pacific Time by default.
Contra Collective was founded in 2020. The enterprise engineering practice came first; the open-source product lab was spun up in late 2024 after the internal toolchain had matured enough to be useful outside of client engagements. The first external release — an early Contra Swarm preview — shipped to GitHub in February 2026.
For enterprise engagements, AI architecture engagements, or agency inquiries: hello@contracollective.com or visit contracollective.com. For open-source issues, feature requests, and developer-tool support: open an issue on the relevant GitHub repo at github.com/Contra-Collective. General press, partnerships, and community: X @contracollectiv or LinkedIn (linkedin.com/company/contracollective).
We hire senior engineers and architects on a project basis for enterprise engagements, and occasionally take on full-time hires in agentic systems, commerce engineering, and platform infrastructure. If that matches your background, email hello@contracollective.com with a link to your work — GitHub, writing, or shipped systems matter more than a traditional résumé.
contracollective.dev vs contracollective.com
Same company, two faces. contracollective.com is the enterprise-facing site — case studies, service offerings, agency engagements, the AI architecture practice. contracollective.dev is the developer-facing product lab — open-source tools, CLIs, product pages, engineering blog, and the runtime infrastructure the agency maintains publicly. The two domains share a single Knowledge Graph entity in Google via identical Organization structured data. When you see "Contra Collective" referenced on either site, it's the same legal entity, same team, same Los Angeles HQ.
Yes — that's the point. The open-source tools on contracollective.dev are free for anyone to clone, run, fork, and ship in production. There is no gate, no "contact sales" wall, no free-tier throttle. Most users never touch the agency side at all. The agency and the product lab are not a funnel; they're a feedback loop. Agency engagements harden the tools. The tools attract developers. Some of those developers eventually end up at companies that need agency-level work, and the loop closes.
No. Every open-source project has public issue tracking, documentation, and release notes on GitHub. Community support is the default path. If you want dedicated support, SLAs, private deployments, or custom integrations for your specific stack, the agency at contracollective.com handles that — but it is strictly optional.
Projects & Open Source
The product-lab roster currently includes: • Contra Swarm — production-grade multi-agent orchestration runtime (typed graphs, durable state, observability-first). • Switchboard — per-environment configuration router used internally to manage dozens of concurrent client engagements. • Linear CLI — terminal-first interface for Linear, the delivery-tracking backbone for every agency project. • ShellShade — terminal theming tool for engineers who work across many client environments daily. • GChat CLI — command-line interface for Google Chat; built for engineering teams running client comms from the terminal. • Shopify Monitor — watchdog for Shopify Plus stores: price, inventory, and deployment changes in real time. Full details on each are at contracollective.dev/projects.
The developer tools published at contracollective.dev are open-source under permissive licenses (typically MIT or Apache 2.0 — check each repo for specifics). Some flagship products have a split model: open-source core with commercial extensions for enterprise features like SSO, audit logging, or dedicated support. This is documented per-project.
Each repository on github.com/Contra-Collective accepts issues and pull requests. Start by reading the CONTRIBUTING.md in the repo you want to work on — it covers the commit conventions, testing expectations, and the path to getting a change reviewed. For non-trivial features, open a discussion before writing code; we'd rather align on direction than watch you burn a weekend. We credit external contributors in release notes and on the project pages. Recurring high-quality contributors get commit access.
The agency stack reflects what enterprise clients run: TypeScript, React, Next.js, Nuxt, Python, FastAPI, Go, Rust, Flutter, Node.js, Docker, Kubernetes. On the AI side: LangGraph, LangChain, OpenAI, Anthropic, and custom orchestration layers. On the commerce side: Shopify Plus, Salesforce Commerce Cloud (SFCC), headless architectures, and ERP integrations across NetSuite and SAP. The open-source product lab mirrors this — we pick the best tool for the job rather than enforcing a single stack.
Yes. Every project shipped on contracollective.dev is either currently running in an enterprise client environment or has graduated from one. Contra Swarm powers autonomous workflows we've deployed for clients. Switchboard routes configuration across every active engagement. Linear CLI is the daily interface for the delivery team. Dogfooding is not a slogan here; it's a prerequisite for a tool getting open-sourced in the first place.
Licensing, Pricing & Commercial Use
The open-source tools are free to use in personal and commercial projects under their licenses. There is no per-seat fee, no usage throttling, no "contact us for commercial pricing" on the core. For projects with a commercial tier, the free/open-source version is genuinely production-capable — the paid tier adds enterprise features (SSO, audit logging, dedicated SLA support) rather than unlocking the core functionality.
Yes. Permissive licensing means you can embed Contra Collective tools in your own commercial products, closed-source systems, and internal platforms without separate licensing arrangements. If you redistribute modified versions, follow the license terms (typically attribution). If you're unsure about a specific scenario, email hello@contracollective.com — we prefer direct answers over license lawyering.
Yes, through the agency side. Enterprise support contracts typically cover: guaranteed response times, private issue triage, priority on roadmap items, security advisory notifications, and optional on-call integration with your team's incident response. Contracts are priced per-tool and per-deployment-size. Contact hello@contracollective.com to scope.
No telemetry by default. CLIs and local tools do not phone home. Anything that requires a cloud component is documented explicitly and opt-in. We don't run analytics on tool usage, we don't collect crash reports without consent, and we don't sell or share any information. Privacy and local-first execution are architectural defaults, not marketing talking points.
Brand & Identity
Yes. Contra Collective, ContraCollective, contracollective, and Contra Collective Agency all refer to the same entity. The legal name is Contra Collective; the trading name across social platforms is Contra Collective Agency. The canonical domains are contracollective.com (agency), contracollective.dev (product lab), and contracollective.news (engineering updates).
LinkedIn: linkedin.com/company/contracollective X (Twitter): @contracollectiv GitHub: github.com/Contra-Collective Instagram: @contracollectiveagency YouTube: @ContraCollectiveAgency Facebook: facebook.com/contracollectiveagency Medium: medium.com/@contracollective Threads: @contracollectiveagency
Still have questions?
Can't find what you're looking for? Reach out and we'll get back to you.
Get in Touch