Blog

ColdBox Free Tip #6 - Using Routing with Wildcard Domains

Victor Campos September 23, 2025

Spread the word

Victor Campos

September 23, 2025

Spread the word


Share your thoughts

102 ColdBox Tips and Tricks by Luis Majano

Domain-Specific Routing with ColdBox!

ColdBox gives you the flexibility to create domain-specific routes, making it perfect for multi-tenant applications or projects that need to respond differently based on the domain or subdomain being accessed. In this tip, we’ll dive into how to use the withDomain() method to create routes that match specific domains or sub-domains.

Domain-Specific Routing

By using ColdBox's withDomain() method in your router, you can define routes that match against incoming domains. This is incredibly useful for multi-tenant applications, where each client has its own subdomain, or any project where domain-based routing is needed.

How to Use withDomain() in Routing

Here’s an example of how you can use domain-based routing in ColdBox:

route( "/" )
  .withDomain( ":client.myapp.io" )
  .to( "client.show" );

In this case, the :client placeholder in the domain will be dynamically filled with the subdomain, and the value will automatically be available in the Request Collection (rc).

For example:

  • Request URLortus.myapp.io
  • rc.clientortus

This makes it easy to handle different client subdomains dynamically in your SaaS or multi-tenant application.

Why Use Domain-Specific Routing?

  • Multi-tenant Support: Perfect for applicatios where each tenant has a unique subdomain.
  • Dynamic Routing: Allows you to dynamically extract domain values and use them in your logic (e.g., to load specific client data).
  • Flexibility: The withDomain() method supports placeholders and wildcards, giving you total control over how domains are routed.

With ColdBox, creating powerful domain-specific routing is a breeze. This feature makes managing multi-tenant apps or subdomain-based routing much simpler. Try it out in your next project!

Learn More ColdBox Tips and Tricks

Stay tuned for more ColdBox tips in our ongoing series. if you want to learn more than 10 free tips and tricks make sure to get your “ColdBox 102 tips and tricks book” We have a variety of formats you can choose from.

Get your Copy

Join the Ortus Community

Be part of the movement shaping the future of web development. Stay connected and receive the latest updates on, product launches, tool updates, promo services and much more.

Subscribe to our newsletter for exclusive content.

Follow Us on Social media and don’t miss any news and updates:

Add Your Comment

Recent Entries

MatchBox and WebAssembly: Running BoxLang in the Browser and at the Edge

MatchBox and WebAssembly: Running BoxLang in the Browser and at the Edge

The MatchBox open beta is live at https://boxlang.ortusbooks.com/boxlang-framework/matchbox, and it brings something genuinely new to the BoxLang ecosystem: a path into WebAssembly.

That means BoxLang code can now move into browser applications, static-site deployments, edge runtimes, and WASI-style containers - without requiring a JVM. The feature is still beta, but the core direction is already useful: write BoxLang, compile it with MatchBox, and ship the generated WASM artifact to wherever a small portable runtime makes sense.

Jacob Beers
Jacob Beers
June 04, 2026
One Language, Every Runtime: BoxLang Expands Beyond the Server

One Language, Every Runtime: BoxLang Expands Beyond the Server

Discover how BoxLang’s multi-runtime architecture helps developers build beyond the server with support for serverless functions, desktop applications, CI/CD workflows, Java integrations, containers, runtime management, and more.

Maria Jose Herrera
Maria Jose Herrera
June 04, 2026