Tools we use to build software
The tools named on the Bytesnitch posters are the stack this page is allowed to talk about. We do not pad the list with products that never appear in the designs.
What the designs actually name
For product surfaces, the site talks about websites, web applications and iOS and Android apps, native and cross-platform. For the release and runtime side, the services tile names CI/CD, Docker, Kubernetes, AWS and more, and the DevOps illustration adds Linux. For connections, the APIs poster names Stripe, PayPal, Razorpay, AWS, Google Cloud, Firebase, CRM and ERP tools, Slack, WhatsApp, email, SMS, Google Sheets and Analytics.
Custom business software talks about CRM, ERP, inventory and workflow automation, aimed at retail and e-commerce, healthcare, education, logistics and manufacturing operations. AI and automation uses the October 2026 definition of an agent that can plan, use tools and act with limited supervision. Those tools are reached through the same APIs, not through a separate unnamed platform.
This website itself is a static export of a Next.js app, with a small Fastify service that only stores contact enquiries in SQLite and sends mail. That is an implementation detail of the marketing site, not a stack we force onto your product. Your product’s languages and hosts are chosen in the project, then described back to you in the same plain words. If a tool is not named on a poster, it is not claimed here.
For how those tools show up in a live product conversation, read the matching service page or send the contact form with the service that fits.
