​
Software and Technologies Used

This document provides a comprehensive overview of all the software, tools, and technologies used in the Billy project, including their purposes, types, and privacy information.

​
Infrastructure & Hosting

​
CloudFlare

  • Purpose: DNS, Message Queuing, CDN, Workers, Tunnels
  • Type: Infrastructure (IaaS)
  • Privacy: Privacy Policy
  • License: Proprietary
  • Usage: Global CDN, DNS management, edge computing, tunnel services

​
Vercel

  • Purpose: Hosting, Monitoring, WAF, Analytics, Storage
  • Type: Infrastructure (IaaS)
  • Privacy: Privacy Policy
  • License: Proprietary
  • Usage: Next.js deployment, serverless functions, preview deployments

​
Supabase

  • Purpose: Database, Authentication, Storage
  • Type: Infrastructure (IaaS)
  • Privacy: Privacy Policy
  • License: Apache License 2.0
  • Usage: PostgreSQL database, user authentication, file storage

​
Upstash

  • Purpose: Database, Message Queuing
  • Type: Infrastructure (IaaS)
  • Privacy: Privacy Policy
  • License: Proprietary
  • Usage: Redis database, message queuing, caching

​
Heroku

  • Purpose: Hosting
  • Type: Infrastructure (IaaS)
  • Privacy: Privacy Policy
  • License: Proprietary
  • Usage: Legacy hosting services

​
Development Tools & Services

​
Checkly

  • Purpose: Monitoring, Testing
  • Type: Tool (SaaS)
  • Privacy: Privacy Policy
  • License: Proprietary
  • Usage: Uptime monitoring, API testing, performance monitoring

​
Mapbox

  • Purpose: Address lookup, Geocoding
  • Type: Tool (SaaS)
  • Privacy: Privacy Policy
  • License: Proprietary
  • Usage: Address validation, map services, location data

​
Resend

  • Purpose: Email delivery
  • Type: Tool (SaaS)
  • Privacy: Privacy Policy
  • License: Proprietary
  • Usage: Transactional emails, email templates, delivery tracking

​
Mintlify

  • Purpose: Documentation platform
  • Type: Tool (SaaS)
  • Privacy: Security & Privacy
  • License: Proprietary
  • Usage: Developer documentation, API reference, knowledge base

​
Sentry

  • Purpose: Error monitoring, Performance tracking
  • Type: Tool (SaaS)
  • Privacy: Privacy Policy (EU Data Residency)
  • License: Apache License 2.0
  • Usage: Error tracking, performance monitoring, crash reporting

​
Loco (localise.biz)

  • Purpose: Translation management
  • Type: Tool (SaaS)
  • Privacy: Privacy Policy
  • License: Proprietary
  • Usage: Internationalization, translation workflows, localization

​
Stripe

  • Purpose: Payment processing, Billing
  • Type: Tool (SaaS)
  • Privacy: Privacy Policy
  • License: Proprietary
  • Usage: Payment processing, subscription billing, financial operations

​
Hookdeck

  • Purpose: Webhook management
  • Type: Tool (SaaS)
  • Privacy: Privacy Policy
  • License: Proprietary
  • Usage: Webhook testing, delivery monitoring, retry logic

​
Inngest

  • Purpose: Message queuing, Job orchestration
  • Type: Tool (SaaS)
  • Privacy: Privacy Policy
  • License: Proprietary
  • Usage: Background job processing, workflow orchestration

​
Figma

  • Purpose: Design, UI/UX
  • Type: Tool (SaaS)
  • Privacy: Privacy Policy
  • License: Proprietary
  • Usage: UI design, component design, design system management

​
Development Frameworks & Libraries

​
Next.js

  • Purpose: React framework
  • Type: Coding framework
  • Privacy: N/A
  • License: MIT
  • Usage: Full-stack React applications, server-side rendering, API routes

​
Turborepo

  • Purpose: Monorepo management
  • Type: Coding tool
  • Privacy: N/A
  • License: MIT
  • Usage: Workspace management, build optimization, task orchestration

​
TypeScript

  • Purpose: Programming language
  • Type: Coding language
  • Privacy: N/A
  • License: Apache License 2.0
  • Usage: Type-safe JavaScript development, static analysis

​
Tailwind CSS

  • Purpose: CSS framework
  • Type: Coding framework
  • Privacy: N/A
  • License: MIT
  • Usage: Utility-first CSS, responsive design, design system

​
GraphQL

  • Purpose: Query language
  • Type: Coding technology
  • Privacy: N/A
  • License: MIT
  • Usage: Internal API, data fetching, schema definition

​
Zod

  • Purpose: Schema validation
  • Type: Coding library
  • Privacy: N/A
  • License: MIT
  • Usage: Runtime validation, type inference, data parsing

​
Storybook

  • Purpose: Component development
  • Type: Coding tool
  • Privacy: N/A
  • License: MIT
  • Usage: Component documentation, testing, development environment

​
Vitest

  • Purpose: Unit testing
  • Type: Coding tool
  • Privacy: N/A
  • License: MIT
  • Usage: Test runner, mocking, coverage reporting

​
Self-Hosted & Local Tools

​
Gotenberg

  • Purpose: PDF generation
  • Type: Self-hosted service
  • Privacy: N/A
  • License: MIT
  • Usage: HTML to PDF conversion, document generation

​
Visual Studio Code

  • Purpose: Integrated development environment
  • Type: Mac Application
  • Privacy: N/A
  • License: MIT
  • Usage: Code editing, debugging, extensions

​
iTerm2

  • Purpose: Terminal emulator
  • Type: Mac Application
  • Privacy: N/A
  • License: GNU
  • Usage: Command line interface, terminal multiplexing

​
Communication & Collaboration

​
Slack

  • Purpose: Team communication
  • Type: Tool (SaaS + Mac Application)
  • Privacy: Privacy Policy (EU Data Residency)
  • License: Proprietary
  • Usage: Team chat, integrations, notifications

​
1Password

  • Purpose: Credential management
  • Type: Tool (SaaS + Mac Application)
  • Privacy: Privacy Policy (EU Data Residency)
  • License: Proprietary
  • Usage: Password management, secure sharing, team access

​
Google Workspace

  • Purpose: Collaboration tools
  • Type: Tool (SaaS)
  • Privacy: Privacy Policy
  • License: Proprietary
  • Usage: Email, documents, calendar, collaboration

​
Analytics & Monitoring

​
Chartbrew

  • Purpose: Data visualization
  • Type: Tool (SaaS)
  • Privacy: Privacy Policy
  • License: Proprietary
  • Usage: Business intelligence, reporting, data dashboards

​
GitGuardians

  • Purpose: Security scanning
  • Type: Tool (SaaS)
  • Privacy: Privacy Policy
  • License: Proprietary
  • Usage: Secret detection, security monitoring, compliance

​
GitHub

  • Purpose: Code repository, Security
  • Type: Tool (SaaS)
  • Privacy: Privacy Policy
  • License: Proprietary
  • Usage: Version control, issue tracking, CI/CD

​
Integration Partners

​
Amazon

​
Amazon Seller

​
Chorus Pro

​
Harvest

​
HubSpot

​
Salesforce

​
Sellsy

​
Zoho

​
Privacy & Security Considerations

​
Data Residency

  • EU Data Residency: Sentry, Slack, 1Password
  • Global: Most other services
  • Local: Self-hosted services

​
Compliance

  • GDPR: All services with EU data residency
  • SOC 2: Vercel, Supabase, Stripe
  • ISO 27001: Various services

​
Security Features

  • 2FA: Available on most services
  • SSO: Enterprise accounts support
  • Audit Logs: Available on most services
  • Encryption: End-to-end where applicable

​
Cost & Licensing

​
Open Source (Free)

  • Next.js, Turborepo, TypeScript, Tailwind CSS, GraphQL, Zod, Storybook, Vitest, Gotenberg, VS Code, iTerm2

​
Proprietary (Paid)

  • CloudFlare, Vercel, Supabase, Upstash, Heroku, Checkly, Mapbox, Resend, Mintlify, Sentry, Loco, Stripe, Hookdeck, Inngest, Figma, Slack, 1Password, Google Workspace, Chartbrew, GitGuardians, GitHub

​
Pricing Models

  • Usage-based: CloudFlare, Vercel, Supabase, Upstash
  • Per-user: Slack, 1Password, Google Workspace
  • Tiered: Most SaaS tools
  • Enterprise: Custom pricing for large organizations

​
Maintenance & Updates

​
Version Management

  • Regular Updates: All tools receive regular updates
  • Security Patches: Critical security updates are applied immediately
  • Feature Updates: New features are evaluated before adoption

​
Dependency Management

  • Automated Updates: Dependabot and similar tools for automated updates
  • Manual Review: Security updates are manually reviewed
  • Testing: Updates are tested in staging before production

​
End-of-Life Planning

  • Deprecation Notices: Services provide advance notice of deprecation
  • Migration Plans: Alternative solutions are identified before deprecation
  • Data Export: Data export capabilities are maintained
This document is maintained by the Billy development team. For questions about specific technologies or privacy concerns, contact the team on Slack: #squad-billy.