GITNUXSOFTWARE ADVICE
Technology Digital MediaTop 10 Best Create A Software of 2026
Explore top tools to create software.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
GitHub
Pull Requests with required status checks and branch protection
Built for software teams needing Git collaboration, review, and automated delivery pipelines.
GitLab
Merge Request pipelines that run automated checks before code can be merged
Built for teams needing integrated CI/CD and DevSecOps workflow around Git.
Bitbucket
Protected branches with required pull request approvals and build status gating
Built for teams managing Git repositories with policy-driven reviews and CI.
Related reading
Comparison Table
This comparison table maps Create A Software against core development and productivity tools, including GitHub, GitLab, Bitbucket, Atlassian Jira, Atlassian Confluence, and related ecosystems. It highlights how each option supports code hosting, team workflows, project tracking, and documentation so teams can evaluate fit for planning, collaboration, and delivery.
| # | Tool | Category | Overall | Features | Ease of Use | Value |
|---|---|---|---|---|---|---|
| 1 | GitHub Hosts Git repositories, supports pull requests and code reviews, and provides automation for building and releasing software. | code hosting | 9.1/10 | 9.5/10 | 8.7/10 | 8.9/10 |
| 2 | GitLab Provides source control, CI/CD pipelines, issue tracking, and package registries for end to end software delivery. | DevOps platform | 8.1/10 | 8.6/10 | 7.9/10 | 7.5/10 |
| 3 | Bitbucket Delivers Git repositories plus branching workflows, pull request reviews, and pipeline support for software development teams. | repository hosting | 8.1/10 | 8.3/10 | 7.8/10 | 8.0/10 |
| 4 | Atlassian Jira Manages agile work with customizable issue workflows, roadmaps, and backlog planning for software teams. | project management | 8.2/10 | 8.8/10 | 7.8/10 | 7.9/10 |
| 5 | Atlassian Confluence Creates and organizes team documentation with pages, knowledge bases, and collaboration features connected to development work. | collaboration docs | 8.2/10 | 8.6/10 | 8.2/10 | 7.6/10 |
| 6 | Linear Tracks issues and roadmap work with fast workflows, sprint visibility, and integrations for software delivery teams. | issue tracking | 8.2/10 | 8.4/10 | 8.7/10 | 7.4/10 |
| 7 | Figma Designs user interfaces with collaborative editing, component libraries, and handoff-ready assets for product builds. | UI design | 8.3/10 | 8.7/10 | 8.2/10 | 7.7/10 |
| 8 | Trello Runs lightweight Kanban boards for tracking features, bugs, and workflows through moveable cards and automation. | kanban | 8.3/10 | 8.2/10 | 9.1/10 | 7.6/10 |
| 9 | Heroku Deploys and runs web applications from Git with managed runtime services and add-on integrations. | app hosting | 8.3/10 | 8.4/10 | 8.7/10 | 7.6/10 |
| 10 | Render Deploys web services, background workers, and static sites with automatic builds from source and managed runtime scaling. | deployment platform | 7.8/10 | 8.0/10 | 8.1/10 | 7.3/10 |
Hosts Git repositories, supports pull requests and code reviews, and provides automation for building and releasing software.
Provides source control, CI/CD pipelines, issue tracking, and package registries for end to end software delivery.
Delivers Git repositories plus branching workflows, pull request reviews, and pipeline support for software development teams.
Manages agile work with customizable issue workflows, roadmaps, and backlog planning for software teams.
Creates and organizes team documentation with pages, knowledge bases, and collaboration features connected to development work.
Tracks issues and roadmap work with fast workflows, sprint visibility, and integrations for software delivery teams.
Designs user interfaces with collaborative editing, component libraries, and handoff-ready assets for product builds.
Runs lightweight Kanban boards for tracking features, bugs, and workflows through moveable cards and automation.
Deploys and runs web applications from Git with managed runtime services and add-on integrations.
Deploys web services, background workers, and static sites with automatic builds from source and managed runtime scaling.
GitHub
code hostingHosts Git repositories, supports pull requests and code reviews, and provides automation for building and releasing software.
Pull Requests with required status checks and branch protection
GitHub stands out for turning Git-based development into a collaboration workflow with pull requests, review tooling, and repository automation. It supports source control, issue tracking, code reviews, and CI/CD integrations through GitHub Actions. It also provides package publishing, code scanning, and security alerts for many common development needs. The platform scales from small teams to large organizations using permissions, branches, and protected workflows.
Pros
- Pull requests enable structured review with diffs, comments, and approvals
- GitHub Actions automates CI and CD with reusable workflows
- Protected branches enforce rules like required checks and review count
- Advanced code search supports quick navigation across large repositories
- Security features like code scanning help catch common vulnerabilities early
Cons
- Workflow setup can become complex with many dependent actions and checks
- Repository permission models require careful governance to prevent access mistakes
- Managing large monorepos can create performance and maintenance overhead
Best For
Software teams needing Git collaboration, review, and automated delivery pipelines
More related reading
GitLab
DevOps platformProvides source control, CI/CD pipelines, issue tracking, and package registries for end to end software delivery.
Merge Request pipelines that run automated checks before code can be merged
GitLab stands out by unifying source control, CI/CD, and DevSecOps workflow in a single application with one integrated interface. It supports end-to-end software delivery with pipelines, merge requests, code review, security scanning, and environment deployments. Built-in project management, wikis, and issue tracking reduce tool sprawl for teams that run software on the same platform. Its automation and extensibility make it practical for complex workflows that span build, test, security checks, and release.
Pros
- All-in-one workflow covers repos, CI/CD, reviews, and security checks
- Pipeline configuration supports reusable components and complex job graphs
- Granular permission model supports protected branches and role-based access
Cons
- Self-managed setups require more operational effort than hosted alternatives
- Advanced pipeline debugging can be slow when job orchestration is complex
- Feature depth can overwhelm teams that only need basic Git hosting
Best For
Teams needing integrated CI/CD and DevSecOps workflow around Git
Bitbucket
repository hostingDelivers Git repositories plus branching workflows, pull request reviews, and pipeline support for software development teams.
Protected branches with required pull request approvals and build status gating
Bitbucket stands out with first-party Git hosting plus tightly integrated pull request workflows for teams that rely on Git. It includes branch-level permissions, code review controls, and CI pipeline support that works directly from repositories. The platform also supports issue tracking and workspace collaboration features that connect changes to work items. Admins can manage access centrally and enforce repository standards through configurable settings.
Pros
- Strong pull request review workflows with diffs, approvals, and build status checks
- Granular repository permissions for branches, groups, and protected branches
- Integrated CI pipelines that trigger on commits and pull requests
Cons
- More complex administration than lighter Git hosts with fewer governance options
- Advanced workflow setup requires careful configuration across repositories and pipelines
- UI can feel dense for users focused only on basic Git hosting
Best For
Teams managing Git repositories with policy-driven reviews and CI
More related reading
Atlassian Jira
project managementManages agile work with customizable issue workflows, roadmaps, and backlog planning for software teams.
Jira workflow engine with automation, conditions, and transition validations
Atlassian Jira stands out for turning issue tracking into a configurable workflow system with strong reporting and cross-team visibility. Teams can manage software development with Scrum and Kanban boards, enforce workflow states with automation rules, and link work to releases and commits using common integrations. Jira also supports granular permissions, custom fields, and audit-friendly change history across projects.
Pros
- Highly configurable workflows with state transitions and approvals
- Scrum and Kanban boards with dependable reporting and filters
- Automation rules reduce manual status updates and routing
- Strong issue linking, including epic and parent hierarchies
- Granular permissions support complex project governance
Cons
- Workflow configuration can become complex for new administrators
- Reporting can feel fragmented without consistent data modeling
- Cross-tool setup takes planning for Jira to reflect real processes
Best For
Product and software teams needing configurable workflows and traceable delivery work
Atlassian Confluence
collaboration docsCreates and organizes team documentation with pages, knowledge bases, and collaboration features connected to development work.
Jira issue macros embed live ticket content directly into Confluence pages
Confluence stands out with wiki-style pages plus tight integration with Jira for turning requirements and decisions into searchable documentation. Teams can create structured pages using templates, embed Jira issues, and manage permissions by space. It also supports real-time collaboration features like page comments and inline edits, alongside advanced knowledge management like macros and page hierarchy.
Pros
- Jira-linked documentation keeps specs, tickets, and decisions connected
- Page templates and macros speed up consistent documentation across teams
- Strong search and permissions support usable organization at scale
Cons
- Maintaining governance across many spaces can become operationally heavy
- Advanced workflows often require add-ons or Jira-centric processes
- Large knowledge bases can feel noisy without disciplined information architecture
Best For
Product and engineering teams building Jira-connected documentation hubs
Linear
issue trackingTracks issues and roadmap work with fast workflows, sprint visibility, and integrations for software delivery teams.
Cycles for time-boxed planning and prioritization
Linear stands out for turning issue tracking into a fast, opinionated planning and execution workspace. Teams create and organize work with issues, prioritize via cycles, and connect related changes and conversations in one place. Built-in workflow views and integrations support roadmapping and developer collaboration without heavy configuration. The result is a product and engineering system designed for clarity and speed over customization depth.
Pros
- Issue views are optimized for planning, prioritization, and quick status scanning
- Cycles and roadmap-style organization keep work aligned across teams
- Tight developer integration links issues with commits and pull requests effectively
Cons
- Workflow customization options are limited compared with fully modular trackers
- Advanced reporting requires more setup than spreadsheet-first or BI-centric tools
- Multi-organization program management workflows can feel rigid
Best For
Product and engineering teams managing delivery with minimal process overhead
More related reading
Figma
UI designDesigns user interfaces with collaborative editing, component libraries, and handoff-ready assets for product builds.
Auto-layout with component variants for responsive design systems
Figma stands out for collaborative design in a single browser workspace with real-time multi-user editing. It supports vector design, prototyping, and design system workflows using components, variants, and auto-layout. Teams can hand off specs through Inspect panels and automate documentation with reusable libraries.
Pros
- Real-time co-editing with presence, comments, and version history
- Strong prototyping with interactive links and component-aware behaviors
- Auto-layout and variants keep responsive components consistent
Cons
- Heavy files can lag, especially with many layers and instances
- Advanced workflows require setup discipline for libraries and naming
- Developer handoff can stall without agreed measurement and component usage
Best For
Product teams building UI designs, prototypes, and shared component systems
Trello
kanbanRuns lightweight Kanban boards for tracking features, bugs, and workflows through moveable cards and automation.
Butler automation rules for moving cards, updating fields, and triggering actions
Trello stands out with a drag-and-drop board layout that maps tasks to columns like Kanban workflows. It supports cards, checklists, due dates, labels, attachments, file links, and member assignments for lightweight project tracking. Power-ups add integrations such as calendars, automation via Butler, and external data connections that extend boards without building code. Collaboration features like comments, mentions, and activity timelines keep teams aligned across shared boards.
Pros
- Visual Kanban boards make workflow design fast and intuitive
- Cards support checklists, labels, due dates, and attachments
- Butler automations reduce repetitive moves and updates
- Mentions and comments centralize team communication per card
- Power-ups extend boards with calendars, analytics, and integrations
Cons
- Complex dependencies and advanced planning need workarounds or other tools
- Reporting is limited compared with dedicated PM and BI platforms
- Permissions and governance across many boards can become cumbersome
Best For
Teams needing visual task tracking and simple workflow automation
More related reading
Heroku
app hostingDeploys and runs web applications from Git with managed runtime services and add-on integrations.
Buildpacks that detect apps and generate runnable environments automatically
Heroku stands out for its app-centric deployment model built around Git pushes and a streamlined platform-as-a-service workflow. It supports multiple runtimes with buildpacks, container image deployments, and add-ons for common infrastructure needs. Teams can scale web and worker processes with platform-native tooling, while CI integrations and logs provide fast feedback during releases.
Pros
- Git-based deployments and release pipeline reduce friction for frequent updates
- Buildpacks support many languages and frameworks without manual runtime setup
- Integrated logging and metrics speed up debugging across dyno types
Cons
- Operational details and scaling behavior can become opaque at higher complexity
- Vendor add-on ecosystem can narrow architecture choices for advanced setups
- Limited native workflow automation compared with full CI/CD and platform tooling
Best For
Small to mid-size teams shipping web apps with fast deployment cycles
Render
deployment platformDeploys web services, background workers, and static sites with automatic builds from source and managed runtime scaling.
Automated preview environments tied to Git commits
Render stands out for deploying full-stack web services with Git-based workflows and production-ready defaults. It supports containerized deployments plus native builds, and it integrates networking, environment variables, and automated rollbacks. The platform also includes background jobs and scheduled tasks, which reduces the glue code needed for common app architectures. Horizontal scaling is built in for web services, making it practical for workloads that change with traffic.
Pros
- Git-based deployments with fast previews for change validation
- Native web service scaling with traffic-driven horizontal expansion
- Background jobs and scheduled tasks in the same platform
Cons
- Less control than Kubernetes for operators needing deep orchestration
- Secrets and environment management can feel fragmented across resources
- Advanced networking and routing require more setup for complex topologies
Best For
Teams deploying web apps plus jobs without running infrastructure-heavy platforms
Conclusion
After evaluating 10 technology digital media, GitHub stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right Create A Software
This buyer's guide helps teams choose software-creation platforms and developer workspaces spanning source control, issue management, documentation, design, and deployment workflows. It covers GitHub, GitLab, Bitbucket, Jira, Confluence, Linear, Figma, Trello, Heroku, and Render. The guide maps concrete capabilities like pull request gating, merge request pipelines, Jira workflow automation, and Git-based preview deployments to the right team use cases.
What Is Create A Software?
Create A Software is the set of tools used to plan work, manage code changes, collaborate on reviews and documentation, and ship applications through automated delivery workflows. It typically covers developer collaboration in Git platforms like GitHub and Bitbucket, plus work tracking in systems like Jira or Linear. It also often includes documentation hubs like Confluence and release execution layers like Heroku or Render. Teams use these systems to reduce coordination friction between planning, code review, validation, and deployment.
Key Features to Look For
These features determine whether software creation stays coordinated from planning to merge to deployment.
Pull request gating with required checks and approvals
Pull request gating ensures code cannot merge until review and automated validations pass. GitHub supports pull requests with required status checks and protected branches, while Bitbucket enforces protected branches with required pull request approvals and build status gating.
Merge request pipelines that run automated checks before merge
Pre-merge pipelines prevent broken code from entering main branches by running jobs as part of merge request workflows. GitLab provides merge request pipelines that run automated checks before code can be merged.
Workflow automation for issue and delivery states
Automations reduce manual status updates and enforce consistent transition rules across teams. Jira provides a workflow engine with automation, conditions, and transition validations, while Linear uses cycles for time-boxed planning and prioritization to keep delivery execution aligned.
Jira-linked documentation with embedded live ticket content
Documentation stays connected to requirements and decisions when tickets render inside pages. Confluence embeds Jira issue macros so live ticket content appears directly in documentation pages, which strengthens traceability for product and engineering teams building specification hubs.
Component-aware UI design workflows with responsive variants
Design systems stay consistent when components and variants drive responsive behavior and handoff clarity. Figma supports auto-layout and component variants for responsive design systems and includes an Inspect panel for developer handoff context.
Git-based deployment workflows with automated previews and runnable environments
Automated delivery feedback shortens validation loops by tying environment behavior to commits. Render provides automated preview environments tied to Git commits, and Heroku generates runnable environments automatically through buildpacks that detect apps and assemble the runtime.
How to Choose the Right Create A Software
The right choice depends on whether software creation needs stronger code-review gates, deeper delivery automation, or tighter planning and documentation workflows.
Start with the source-control collaboration model
For teams that need structured code review with branch protection, GitHub and Bitbucket support protected branches and review workflows with diffs, comments, and approvals. For teams that want tightly integrated pre-merge validation, GitLab focuses on merge request pipelines that run automated checks before code can be merged.
Decide how validation should be enforced before code merges
If merge rules must block until CI results and reviewer approvals complete, use GitHub or Bitbucket because protected branches can require status checks and gating. If validation is best expressed as pipeline jobs connected to merge requests, use GitLab so merge request pipelines coordinate build, test, and security checks before merge.
Match planning and workflow depth to team process
For teams that need configurable states and approvals across complex delivery processes, Jira offers a workflow engine with automation rules, conditions, and transition validation. For teams that prefer fast, opinionated execution with minimal configuration, Linear emphasizes cycles for time-boxed planning and optimized issue views that link effectively to commits and pull requests.
Connect decisions to documentation and reduce context switching
If requirements and decisions must stay readable alongside live ticket status, Confluence works with Jira issue macros to embed live ticket content into pages. If the goal is visual product alignment before implementation, Figma supports real-time co-editing, comments, and component variants designed for responsive design systems.
Choose the deployment and preview workflow that fits release frequency
For teams validating changes per commit with disposable previews, Render ties preview environments to Git commits and adds background jobs and scheduled tasks in the same platform. For teams shipping web apps from Git with managed runtime behavior, Heroku uses buildpacks to detect apps and generate runnable environments automatically.
Who Needs Create A Software?
Create A Software tools fit different parts of the delivery pipeline from planning to merge to deployment.
Software teams that need Git collaboration plus strict review and automation
GitHub excels for software teams needing pull requests with required status checks and protected branch rules that enforce review quality. Bitbucket also fits teams managing Git repositories with protected branches, required pull request approvals, and build status gating.
Teams that run CI/CD and DevSecOps workflows tightly coupled to merge requests
GitLab is built for end-to-end delivery with merge request pipelines that run automated checks before code merges. Its integrated workflow covers repos, CI/CD, code review, security scanning, and environment deployments in one interface.
Product and engineering teams that need traceable delivery planning and configurable workflows
Jira is the right match for configurable workflow states with automation rules and transition validations plus strong issue linking across epics and parent hierarchies. Confluence complements Jira by embedding Jira issue macros so specs and decisions remain connected to live ticket content.
Teams that validate product design and align handoff assets before implementation
Figma fits product teams building UI designs, prototypes, and shared component systems with auto-layout and component variants for responsive design systems. Its real-time co-editing and comment threads help teams converge on design intent before code changes begin.
Common Mistakes to Avoid
Common selection failures come from mismatching enforcement style, workflow depth, and collaboration expectations across the toolchain.
Assuming lightweight Git hosting will provide merge enforcement and CI gating
Teams that need required checks and protected branch rules should prioritize GitHub or Bitbucket because both provide branch protection and build status gating for pull requests. Git platforms without strong gating push responsibility onto manual coordination and increase the chance of merges that bypass validation.
Trying to run complex CI/CD pipelines without planning for pipeline complexity
GitLab pipeline configuration can support reusable components and complex job graphs, but advanced debugging can be slow when orchestration becomes complex. Teams with simpler needs often find pipeline depth overwhelming, while GitHub Actions can also become complex when many dependent actions and checks are introduced.
Over-modeling workflows in Jira without a governance approach
Jira workflow configuration can become complex for new administrators, which increases the effort to maintain consistent transition rules. Confluence can also become operationally heavy when governance across many spaces is not disciplined.
Choosing task boards that cannot support real reporting and governance needs
Trello delivers visual Kanban workflow design quickly and adds Butler automation for card moves and field updates. Reporting stays limited compared with dedicated PM and BI systems, and permissions and governance across many boards can become cumbersome.
How We Selected and Ranked These Tools
we evaluated every tool on three sub-dimensions. features carry weight 0.4, ease of use carries weight 0.3, and value carries weight 0.3. the overall rating is the weighted average of those three, computed as overall = 0.40 × features + 0.30 × ease of use + 0.30 × value. GitHub separated itself from lower-ranked tools on features because pull requests support required status checks paired with protected branch enforcement, which directly strengthens merge discipline and delivery automation.
Frequently Asked Questions About Create A Software
How do Git-based tools differ for creating and reviewing software code?
GitHub is built for collaboration with pull requests, required status checks, and branch protection enforced in the same workflow. GitLab provides merge request pipelines that run automated checks before merge, which ties CI and review into one system. Bitbucket supports protected branches with required pull request approvals and build status gating for policy-driven review.
Which tool best fits teams that want DevSecOps steps embedded into the delivery pipeline?
GitLab integrates security scanning and environment deployments directly into the merge request flow. GitHub pairs code scanning and security alerts with CI/CD through GitHub Actions so security checks run alongside delivery. Bitbucket focuses on repository governance and pull request workflows while still supporting CI pipeline support from repositories.
What tool supports end-to-end software delivery with fewer separate systems?
GitLab unifies source control, CI/CD, project management, and wikis inside one interface so builds, reviews, security checks, and releases stay connected. GitHub and Bitbucket can connect these components through integrations and automation, but GitLab’s integrated DevSecOps workflow reduces tool sprawl. Jira can centralize delivery work planning, but it does not replace CI/CD orchestration by itself.
How should teams connect product work items to code changes and releases?
Atlassian Jira links work to releases and commits through common integrations, and it retains audit-friendly history using workflow states. Confluence embeds Jira issue macros into documentation so requirements and decisions stay tied to live tickets. GitHub and GitLab connect code reviews and merge requests to the delivery timeline that Jira tracks.
Which platform is best for documenting requirements and decisions alongside live ticket content?
Confluence is designed as a wiki hub with structured pages, templates, and page hierarchy for knowledge management. Jira issue macros let Confluence pages embed ticket content so changes in Jira reflect in documentation. Figma helps with design documentation by pairing specs and inspect panels with the UI work that Jira and Confluence can reference.
What tool supports product and engineering planning with fast, opinionated execution workflow?
Linear focuses on issue tracking with cycles for time-boxed planning and prioritization. Jira supports Scrum and Kanban boards with configurable workflows and automation rules, which fits teams that need more governance. Trello provides a lighter visual system using drag-and-drop boards, but it typically lacks the deeper workflow engine that Jira offers.
Which option is best for designing UI components and collaborating on prototypes in-browser?
Figma supports real-time multi-user editing in a single browser workspace for vector design and prototyping. It builds design systems through components, variants, and auto-layout to keep responsive behavior consistent. Inspect panels help teams hand off specs for implementation, which often pairs well with Jira-linked documentation in Confluence.
How do teams implement lightweight project tracking and simple automation for software tasks?
Trello uses cards and labels on Kanban-style boards to map tasks to clear statuses. Butler automation moves cards, updates fields, and triggers actions without custom code. Jira and Linear also manage execution, but Trello’s drag-and-drop structure is optimized for quick visual task tracking.
Which platform streamlines deployment for small to mid-size web apps using a push workflow?
Heroku deploys apps via a Git push workflow and uses buildpacks to detect apps and generate runnable environments automatically. It supports multiple runtimes and can scale web and worker processes using platform-native tooling. Render also uses Git-based workflows, but it emphasizes production-ready defaults plus automated rollbacks and background jobs.
What is the best choice for deploying web services with previews, jobs, and automated rollbacks?
Render is built for full-stack web services with Git-based production deployments, native builds, and containerized deployments. It provides automated preview environments tied to Git commits and includes background jobs plus scheduled tasks. It also automates rollbacks, which reduces risk during releases compared with managing these behaviors manually through generic tooling.
Tools reviewed
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Technology Digital Media alternatives
See side-by-side comparisons of technology digital media tools and pick the right one for your stack.
Compare technology digital media tools→FOR SOFTWARE VENDORS
Not on this list? Let’s fix that.
Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.
Apply for a ListingWHAT THIS INCLUDES
Where buyers compare
Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.
Editorial write-up
We describe your product in our own words and check the facts before anything goes live.
On-page brand presence
You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.
Kept up to date
We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.