Commissioned Research
Top 10 Best Affordable Custom Software of 2026

GITNUXSOFTWARE REVIEW

Digital Transformation In Industry

Top 10 Best Affordable Custom Software of 2026

Compare affordable custom software options and tradeoffs for teams building internal tools, with Zoho Creator, Glide, and Retool included.

20 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

Search agents gather the source set and the review record, including transcriptions of video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy

Teams building internal tools, customer-facing apps, or lightweight workflows can reduce development cost by choosing a low-code or no-code platform with clear data models, role-based access, and integration paths. This comparison helps evaluators weigh tradeoffs between quick UI delivery and maintainable automation through APIs, schemas, and deployment controls.

Zoho Creator is the best pick for SMB teams building internal CRUD apps and workflow automation because event-driven workflows can react to record lifecycle changes and update related data without middleware. Glide is the strong alternative for teams that want spreadsheet-linked apps with quick, card-based UI updates for light automation.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

Zoho Creator

Event-driven workflows that trigger on record lifecycle changes and update related data without building middleware.

Best for: Fits when teams need internal CRUD apps and workflow automation with deep Zoho integration and API access.

2

Glide

Editor pick

Card-based app layouts tied to underlying spreadsheet records for fast form-to-workflow updates.

Best for: Fits when teams need quick internal workflow apps with light automation and connector-driven integrations.

3

Retool

Editor pick

Resource-based automation that runs queries and scripts from UI actions, schedules, and API calls.

Best for: Fits when teams need internal CRUD workflows with integrated actions and API-driven automation.

Comparison Table

1
Zoho CreatorBest overall
SMB
9.4/10
Overall
2
8.9/10
Overall
3
8.8/10
Overall
4
8.5/10
Overall
5
8.3/10
Overall
6
7.9/10
Overall
7
7.5/10
Overall
8
7.1/10
Overall
9
6.8/10
Overall
10
6.5/10
Overall
#1

Zoho Creator

SMB

Low-code application development platform within the Zoho ecosystem.

9.4/10
Overall
Features9.4/10
Ease of Use9.5/10
Value9.3/10
Standout feature

Event-driven workflows that trigger on record lifecycle changes and update related data without building middleware.

Zoho Creator lets teams build database-backed business apps with forms, reports, and role-based pages for internal workflows. Its visual workflow builder connects to Zoho services and external systems through documented connectors, plus it supports REST API access for custom integrations.

Automation rules run on events like record creation and updates, and the app can be packaged for repeatable deployments across environments. Extensibility comes through custom functions and API endpoints that can be called from external front ends or automation runners.

Pros
  • +Visual workflows for record events reduce custom code for common automation
  • +Strong Zoho integration coverage for identity, data access, and process wiring
  • +REST endpoints and API connectors support external UI and system integration
  • +Granular page and action permissions support RBAC-style access patterns
Cons
  • –Cross-system automation can require careful connector setup to avoid brittle triggers
  • –Complex apps need governance to keep permissions and roles consistent over time
  • –UI customization is less flexible than developer-built front ends for complex layouts
Use scenarios
  • Operations teams

    Track internal requests with approval steps

    Requests routed and monitored

  • RevOps and finance analysts

    Report on custom database metrics

    Recurring operational reporting

Show 1 more scenario
  • IT and integration builders

    Connect apps to external systems via REST

    Systems exchange records

    Create custom integrations by calling REST API endpoints from external tools and automation runners.

Best for: Fits when teams need internal CRUD apps and workflow automation with deep Zoho integration and API access.

#2

Glide

SMB

No-code app builder that turns spreadsheets into functional mobile and web apps.

8.9/10
Overall
Features8.9/10
Ease of Use8.9/10
Value8.9/10
Standout feature

Card-based app layouts tied to underlying spreadsheet records for fast form-to-workflow updates.

Glide targets business teams that want fast internal apps without building a full codebase. It pairs a spreadsheet-style data entry model with visual screens and actions that can call external services.

Glide’s practical automation focus shows up in how interfaces connect to triggers, calculated fields, and workflow-style updates. Extensibility is mainly via connectors and API-based integrations rather than custom hosting control.

Pros
  • +Spreadsheet-like authoring speeds up app creation for operational teams
  • +Visual UI builder supports rapid changes without a separate frontend project
  • +Built-in logic for calculated fields reduces manual data sync
  • +Connector-based integrations cover common SaaS workflows
Cons
  • –Governance depth is limited compared with IDE-based internal tools
  • –API and webhook coverage can be uneven across integration types
  • –Complex, high-volume apps can hit performance and workflow limits
  • –Data modeling flexibility is narrower than custom backend development
Use scenarios
  • Agencies and partner teams

    Share controlled client record views

    Controlled portal updates

  • Operations administrators

    Collect and route approvals for requests

    Approval status stays visible

Show 2 more scenarios
  • Event organizers

    Coordinate staff and attendee tasks

    Event tasks stay aligned

    Build data-backed screens that capture event updates for attendees or staff across a shared app.

  • Field service teams

    Report inspections and update work orders

    Structured field updates captured

    Give field staff guided, mobile-friendly screens to record inspections and update connected work-order data.

Best for: Fits when teams need quick internal workflow apps with light automation and connector-driven integrations.

#3

Retool

SMB

Low-code platform for building internal business tools and dashboards.

8.8/10
Overall
Features8.8/10
Ease of Use8.8/10
Value8.8/10
Standout feature

Resource-based automation that runs queries and scripts from UI actions, schedules, and API calls.

Retool’s core workflow combines a visual interface with backend query steps that can call SQL, REST APIs, or external services and then render results in tables, charts, and forms. Actions can write data through connector operations, and custom scripts can shape payloads and enforce client-side workflow rules before requests run. Extensibility is practical because custom JavaScript and reusable components can be shared across apps, which reduces repeated work in larger teams. Integration depth is strong when apps need mixed data sources and multi-step operations.

A key tradeoff is governance and maintainability when many apps share ad-hoc scripts and loosely standardized query patterns, since small logic differences can fragment debugging and change control. Retool fits best when teams need rapid iteration on internal operations apps that call multiple systems and require interactive approval or review screens.

Pros
  • +High-coverage connector set for wiring UI to data actions
  • +Reusable components and custom code reduce repeated UI logic
  • +Action steps support multi-step workflows across systems
  • +Automation triggers allow scheduled and API-driven executions
Cons
  • –Governance gets harder as apps accumulate scripts and custom query patterns
  • –Complex business logic can become split between queries and scripts
  • –Performance tuning takes effort when many components refresh frequently
  • –Role boundaries require careful resource-level permission setup
Use scenarios
  • Operations analysts and admins

    Build review and approval dashboards

    Faster exception handling

  • Revenue operations teams

    Automate CRM data corrections

    Lower manual cleanup

Show 2 more scenarios
  • Product support teams

    Create case triage tooling

    More consistent triage

    Case views join data from multiple sources and execute follow-up actions from operators.

  • Data engineering teams

    Operationalize data pipelines in UI

    Controlled pipeline operations

    Operators run data read and write steps through scripted actions tied to monitoring views.

Best for: Fits when teams need internal CRUD workflows with integrated actions and API-driven automation.

#4

Webflow

SMB

Visual web development platform generating production HTML, CSS, and JavaScript.

8.5/10
Overall
Features8.5/10
Ease of Use8.5/10
Value8.5/10
Standout feature

CMS collections with template-driven publishing let teams manage structured content and update pages consistently from the same data source.

Webflow combines a visual site builder with code-export friendly publishing workflows, which is distinct versus purely form-based app builders. It supports CMS collections, dynamic pages, and reusable components for content-driven front ends.

Pros
  • +Visual designer produces production-ready page layouts without custom frontend frameworks
  • +CMS collections and templates handle structured content and repeatable layouts
  • +Component and style reuse reduces duplication across large marketing sites
  • +Export-friendly workflow supports moving parts into a developer-maintained codebase
Cons
  • –Application state and business logic are limited inside the editor
  • –Workflow automation is weaker than purpose-built internal tool builders
  • –API surface for deep integrations is limited compared with low-code app platforms
  • –Complex role separation and governance require disciplined workspace management
Use scenarios
  • Design teams

    Prototype CMS-driven app-like pages

    App-like UX without code-first

  • Freelancers and creative agencies

    Publish responsive portfolio layouts

    Branded responsive portfolio published

Show 2 more scenarios
  • Marketing designers

    Ship animated campaign landing pages

    Interactive campaign pages published

    Add visual interactions and animations to marketing pages while keeping page structure in the visual editor.

  • Product marketing teams

    Maintain documentation-style information sites

    Consistent information site

    Create navigable guide and feature pages using repeatable patterns and CMS-driven content structures.

Best for: Fits when teams need a custom content site and lightweight interactive forms, not full internal apps.

#5

Bubble

SMB

Visual programming platform for building full web applications without writing code.

8.3/10
Overall
Features8.3/10
Ease of Use8.3/10
Value8.3/10
Standout feature

Declarative workflow rules can bind UI events to database changes across pages and states.

Bubble fits teams that need an interface-first build process with a persistent database, then iteratively refine UX with workflow rules. The workflow layer connects UI events to database actions, page conditions, and permissions checks. REST API connectors and incoming webhooks help wire external services into the app lifecycle without a separate backend project.

Pros
  • +Visual UI builder paired with declarative workflows for fast iteration
  • +Built-in database and page logic reduce early backend scaffolding
  • +REST connectors and webhooks support practical third-party integrations
  • +Plugin system extends capability without rewriting the whole app
Cons
  • –Complex cross-data workflows can become hard to reason about
  • –Fine-grained backend control is limited compared to custom services
  • –Performance tuning for heavy workloads may require workarounds
  • –Governance and approval patterns often need careful role design
Use scenarios
  • Operations teams

    Manage intake-to-approval workflows

    Fewer manual status updates

  • RevOps teams

    Centralize lead enrichment and routing

    Faster lead follow-up

Show 2 more scenarios
  • Customer support teams

    Ship a searchable case portal

    Reduced ticket handling time

    Database-backed pages with conditional UI support self-serve status and internal triage.

  • Product teams

    Launch validated MVPs with real users

    Shorter build-to-test cycles

    A drag-and-drop UI lets teams iterate screens while workflows handle the app logic.

Best for: Fits when teams need custom web app UX plus workflow-driven business logic.

#6

Ninox

SMB

Low-code database platform for building custom business applications.

7.9/10
Overall
Features7.9/10
Ease of Use7.9/10
Value7.9/10
Standout feature

Ninox automation rules that update records and route tasks based on workflow conditions tied to its database model.

Ninox centers around a data model with tables, relations, and calculated fields that power both UI and business rules. Automation rules can react to record events and run server-side logic like generating documents, updating fields, and routing work across users. Ninox’s integration surface includes REST API access plus webhook triggers for outbound and inbound event handling, with authentication that fits common enterprise patterns like OAuth flows. Administration focuses on user access per workspace and app, with permission controls tied to roles and shared resources.

Pros
  • +Record-centric app builder that links forms, tables, and rules directly
  • +Event-driven automation that runs based on record changes
  • +API and webhook integration for syncing data with external systems
  • +Flexible UI pages designed around the same underlying database
Cons
  • –Custom logic is constrained versus full-code backend development
  • –Advanced governance and audit depth can require careful role design
  • –Complex reporting may demand structured formulas instead of custom queries
  • –Large integration workloads can increase rule and connector maintenance
Use scenarios
  • Operations teams

    Intake to approval workflow

    Faster approvals and fewer manual steps

  • Customer support teams

    Case tracking with SLAs

    Consistent triage and escalation

Show 2 more scenarios
  • IT and business technologists

    App integration with core systems

    Reduced manual data entry

    Webhooks and API endpoints sync records and drive events across tools.

  • Project managers

    Asset and document lifecycle

    Clear ownership and auditability

    Custom pages capture fields and automations manage handoffs and document generation.

Best for: Fits when teams need database-backed workflows with manageable integration and low ops overhead.

#7

Budibase

SMB

Open-source low-code platform for building business applications and internal tools.

7.5/10
Overall
Features7.5/10
Ease of Use7.4/10
Value7.6/10
Standout feature

Self-hosted Budibase deployments with app packaging that run inside an organization’s infrastructure.

Budibase centers on building internal apps with a visual interface that connects forms, tables, and custom UI to external data sources. It supports both self-hosted deployments and cloud-style development workflows by packaging apps into versionable artifacts and running them inside your chosen environment.

Pros
  • +Visual app builder that connects UI components to external data quickly
  • +Self-hosting option supports controlled environments and custom network topology
  • +Workflow actions cover common CRUD operations without custom code for each screen
  • +Connector-based integration reduces glue code between systems
Cons
  • –Complex business rules can become harder to maintain than code-first services
  • –Advanced authorization patterns need careful configuration for each resource
  • –Debugging multi-step workflows is slower than tracing server-side code
  • –Some integrations require additional connector configuration and testing
Use scenarios
  • Agencies and service teams

    Create branded client portal screens

    Portal matches client processes

  • Software developers

    Reuse data operations in other apps

    Data reuse across apps

Show 2 more scenarios
  • Operations and departmental teams

    Run request and approval flows

    Approvals follow a structured path

    Use forms and role-aware steps to submit requests and move records through review states.

  • Operations managers

    Monitor activity with interactive dashboards

    Faster operational decision-making

    Assemble chart and KPI tiles with filters to support drill-down into operational data.

Best for: Fits when teams need internal CRUD apps and light automation with controllable deployment options.

#8

Caspio

SMB

Low-code platform for building database-driven web applications.

7.1/10
Overall
Features7.1/10
Ease of Use7.2/10
Value7.0/10
Standout feature

Caspio’s visual database app builder ties UI components directly to relational data views and computed fields.

Caspio targets teams that need production database apps without building a full custom codebase from scratch. It centers on database-driven application building with form, table, and dashboard components connected to a relational back end.

Pros
  • +Database-first app building keeps UI and data logic aligned
  • +Workflow automation supports trigger-based and scheduled actions
  • +Role-based access controls cover common app security needs
  • +Reporting components handle dashboards and filtered views
Cons
  • –Custom logic outside the visual builder can feel constrained
  • –API-based integrations require careful testing for edge cases
  • –Complex multi-step workflows take more configuration effort
  • –Granular governance controls are not as deep as custom engineering
Use scenarios
  • Project teams

    Manage project records and status

    Project information stays organized

  • Integration-focused business teams

    Exchange application records via APIs

    Apps stay system-connected

Show 2 more scenarios
  • Service desk and approvers

    Intake requests with review routing

    Requests become trackable records

    Collect request records through forms and route them through configured review steps.

  • Business operations teams

    Publish searchable directories from data

    Searchable directory pages

    Turn structured database records into browsable directory views for listings and comparisons.

Best for: Fits when teams need database-backed apps with practical automation and manageable integration effort.

#9

Adalo

SMB

No-code platform for designing and publishing mobile and web applications.

6.8/10
Overall
Features6.8/10
Ease of Use6.8/10
Value6.8/10
Standout feature

App screens can be wired to backend collections and actions through visual bindings, reducing glue code for CRUD apps.

Adalo builds mobile and web apps from a visual UI editor and a connected data layer. It supports database-backed screens with reusable components and built-in user auth for common app patterns.

Pros
  • +Visual builder maps screens directly to app data collections
  • +Built-in authentication supports standard account and session flows
  • +Reusable UI components speed consistent app layout changes
  • +Automation via event triggers and external REST calls
Cons
  • –Automation coverage depends on external services for complex workflows
  • –Advanced UI logic can become limiting versus custom code
  • –Deep API surface requires careful planning for edge-case handling
  • –Cross-app governance needs more manual checks as apps scale
Use scenarios
  • Product designers

    Prototype mobile flows with data interactions

    Testable mobile prototype

  • Customer support teams

    Provide authenticated customer service portals

    Self-service customer experience

Show 2 more scenarios
  • Startup founders

    Validate an MVP with real users

    MVP supports user feedback

    Create an authenticated, data-driven app with interactive flows to gather early user feedback.

  • Small business teams

    Build CRUD record-management apps

    Record management without backend pages

    Deliver apps focused on creating, viewing, editing, and updating records in collections.

Best for: Fits when teams need fast, data-driven mobile apps with light automation and external API connectivity.

#10

FlutterFlow

SMB

Low-code builder for native iOS and Android apps using the Flutter framework.

6.5/10
Overall
Features6.5/10
Ease of Use6.5/10
Value6.5/10
Standout feature

Code export to Flutter and Dart with custom widgets and actions that preserve maintainable extensions.

FlutterFlow focuses on building mobile apps with visual screens plus code export to Dart and integration-friendly widget logic. It includes a declarative way to connect UI actions to backend APIs and data via connectors and custom functions.

Pros
  • +Visual screen builder maps directly to Flutter UI structure
  • +Reusable custom widgets and actions speed consistent UI behavior
  • +Exported code allows targeted imperative extensions
  • +API connectors and webhooks support action-to-backend integration
Cons
  • –Source-level control is uneven across all visual components
  • –Complex domain modeling often requires custom code and careful wiring
  • –Multi-environment configuration needs discipline for release hygiene
  • –Deep admin governance like audit logs and RBAC is limited
Use scenarios
  • Flutter developers

    Customize generated widgets with code

    More control over implementation

  • Startup teams

    Iterate on customer-facing app screens

    Faster screen validation

Show 2 more scenarios
  • Design systems teams

    Standardize multi-screen UI patterns

    Less duplicated UI work

    Create reusable widgets and page patterns to keep application screens consistent across projects.

  • Consumer app builders

    Create profile and social interaction interfaces

    Interactive social app interfaces

    Assemble onboarding, profile, feeds, and messaging screens and extend behavior using code when needed.

Best for: Fits when teams need rapid Flutter app delivery with API-first integrations and selective code control.

Conclusion

After evaluating 10 affordable custom software, Zoho Creator 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.

Our Top Pick
Zoho Creator

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Affordable Custom Software

How do affordable custom software tools compare with a traditional custom build?
Bubble, Retool, and Zoho Creator provide visual builders for database-backed workflows without requiring teams to build every screen and integration from scratch. FlutterFlow offers a different path by exporting Flutter and Dart code, while Budibase supports app packaging for controlled deployment.
Which tools handle integrations and API-driven workflows most effectively?
Retool connects interface actions to queries, scripts, schedules, and API calls, making it suitable for internal workflows that coordinate several systems. Ninox, Zoho Creator, Bubble, and Budibase provide REST or webhook connectivity, while FlutterFlow uses API connectors and custom functions for mobile interfaces.
What security controls should teams verify before deploying a custom app?
Teams should verify authentication, role boundaries, audit requirements, data isolation, and deployment controls in each product rather than assume feature parity. Zoho Creator provides role-based pages, Adalo includes built-in user authentication, and Budibase supports self-hosted deployment, but SSO, SCIM provisioning, and detailed audit features require product-specific validation.
How should existing data be migrated into an affordable custom software platform?
Teams should map source fields to the target schema, preserve record identifiers, and test relationships before importing production data. Glide is suited to spreadsheet-shaped records, while Ninox and Caspio require closer planning when forms, tables, computed fields, and workflow rules depend on a structured database model.
Which platforms provide the clearest controls for administrators and business users?
Zoho Creator combines role-based pages with event-driven record workflows, giving administrators control over access and business actions. Retool exposes application actions through queries, scripts, and schedules, while Bubble supports user roles and configurable experiences across pages.
When does code extensibility matter more than a visual builder?
Code extensions matter when an app needs behavior that standard components and declarative workflows cannot express. FlutterFlow supports custom widgets, custom actions, and Dart export, while Bubble and Retool allow custom code for workflows that exceed their visual configuration.
Where does a visual site builder fall short for internal business software?
Webflow handles CMS collections, dynamic pages, reusable components, search, and forms, but its application logic generally remains outside the editor. Retool, Zoho Creator, and Caspio provide more direct support for internal data operations, record workflows, and administrative interfaces.
What breaks if a team selects a spreadsheet-oriented platform for relational workflows?
Glide can connect screens and actions to spreadsheet-style records, but workflows with complex relationships, computed data, and strict transaction rules may require more careful modeling. Caspio and Ninox provide database-centered structures that better match relational forms, tables, reports, and record-linked automation.
How can a team validate a custom app before wider deployment?
A practical validation cycle starts with one workflow, representative records, role tests, integration failures, and measured response throughput. Budibase supports versionable app packaging, while Zoho Creator supports repeatable deployment across environments and Retool can test actions through queries, scripts, and API calls.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Affordable Custom Software

We separate affordable custom software options by how much control you actually get over your workflows, data, and handoffs. Look for extensibility surface, automation depth, and admin and audit log coverage, because these determine how far “custom” goes after the first setup.

Extensibility via API and connectors

Why it matters

Extensibility via API and connectors matters when you need to wire custom screens, rules, and records into existing tools without fragile workarounds. It’s often the difference between a project that stays maintainable and one that breaks each time you change a workflow.

How to check

Ask for the documentation page that lists available endpoints and auth patterns, then try creating a small call that reads and writes a test record. In the demo, request one real integration scenario (two-way sync or an event) and verify the product can do it with its built-in surface.

Data model and schema customization

Why it matters

Data model and schema customization matters because custom software usually lives or dies on how well it represents your objects, fields, and relationships. If the data structure is too rigid, every change turns into a workaround.

How to check

During the demo, ask how they handle adding a new object type, adding fields, and linking it to existing records. Request a sample configuration or export that shows the resulting fields and constraints for your test case.

Workflow automation with rules and triggers

Why it matters

Workflow automation with rules and triggers is what turns configuration into real throughput for custom processes. Strong automation reduces manual handoffs and keeps the business logic where your team can reason about it.

How to check

Ask for a rule example that runs on create, update, or status change, then show what data it can reference. If they mention triggers, ask for a demo where you change a condition and immediately see the downstream actions update.

Admin, RBAC, and audit log coverage

Why it matters

Admin, RBAC, and audit log coverage matters for affordable custom builds because multiple people will touch configuration and records. Without clear roles and history, you can’t control changes or see what happened when something goes wrong.

How to check

In the demo, request at least three roles with different permissions and verify each role can or cannot change configuration and records. Then ask to view an audit log for a configuration change and confirm it records who changed what and when.

Configuration portability across environments

Why it matters

Configuration portability matters when affordable custom software is maintained over time and moved through staging into production. If configuration can’t travel cleanly, each release becomes risky and labor-heavy.

How to check

Ask how they promote changes from a test workspace to a live one and whether they provide a repeatable import/export path. Request to see what a typical configuration package includes (rules, fields, mappings) and how you roll back when something fails.

Red flags

  • Demo scenarios rely on off-platform steps instead of product automation
  • They cannot show how your specific objects and workflows are represented in the data model
  • Audit and permission controls are not shown end-to-end in the demo

Fit by situation

  • If you need to connect custom workflows to other business systems, prioritize Extensibility via API and connectors.
  • If your processes depend on changing record fields, constraints, and relationships, prioritize Data model and schema customization.
  • If you will have multiple admins changing rules over time, prioritize Admin, RBAC, and audit log coverage.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

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 Listing

WHAT 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.