# Cloudflare adds custom applications to its Application Library for Gateway policies Cloudflare's Application Library now lets administrators define their own applications by hostname, IP subnet, or both, and reference them in Gateway DNS, Network and HTTP policies, alongside search and interface changes. Canonical URL: https://freelancenews.online/news/cloudflare-adds-custom-applications-to-its-application-library-for-4161f63a Published: 2026-10-15T14:17:27.769Z Updated: 2026-10-15T14:17:27.769Z Source published: 2026-10-15T00:00:00.000Z Event date: Not established Review status: source-reviewed Review method: Automated comparison against retrieved source text; not independent fact-checking. ## Report Cloudflare has added support for custom applications to the Application Library, the catalog that administrators use when writing Gateway policies. The change is documented in a changelog entry on the company's developer documentation site, which states that the capability is available "starting today" relative to the post. The core of the release is definition: an administrator can now create an application entry themselves rather than relying only on the applications Cloudflare already catalogues. According to the changelog, a custom application is defined by hostnames, IP subnets, or both. Those definitions are not merely descriptive. The changelog says custom applications can be referenced in Gateway DNS, Network and HTTP policies, which means the entries an administrator creates become selectable objects in the policy builder rather than documentation kept alongside it. The definition can be narrowed further. The changelog states that TCP or UDP ports, or port ranges, can optionally be added to restrict HTTP and Network matching. That optional layer applies to HTTP and Network matching specifically, per the source text. Alongside custom applications, the release covers housekeeping in the same area. Cloudflare says it improved search and filtering in the Application Library, updated the interfaces, data and metrics used to review applications, and made selecting and managing applications in the Gateway policy builder easier. The changelog points readers to two further documentation pages, one on custom applications and one on applications and app types, for more information. Those pages are referenced but their contents are not reproduced in the supplied evidence, so the operational detail they may contain cannot be assessed here. For developers and technical freelancers who administer Cloudflare One environments for clients, the practical effect is that policy objects no longer have to be limited to what the vendor catalogues. An internal tool, a client-specific SaaS endpoint, or a set of subnets that Cloudflare does not list can be represented as a named application and then reused across DNS, Network and HTTP policy rules. The port and port-range option matters for teams that need to distinguish services sharing an address. Because the changelog ties that option to HTTP and Network matching, it is the kind of control that would be relevant when a hostname or subnet hosts more than one service and only some of that traffic should be treated as the application in question. The search, filtering and policy-builder changes are harder to evaluate from the changelog alone. Cloudflare describes them as improvements and as making selection and management easier, but the entry does not quantify them, describe the previous behaviour, or give before-and-after examples, so the size of the change is not established by the evidence. Similarly, the changelog says the interfaces, data and metrics used to review applications were updated. It does not say which metrics changed, what new data appears, or whether any existing views were removed, so administrators should not assume a specific new reporting capability from this text. There is also no pricing, plan or entitlement information in the changelog. The entry does not state which Cloudflare plans include custom applications, whether the feature is gated, or whether any limits apply to the number of custom applications an account can define. Those are open questions for anyone planning a rollout. No migration or breaking-change guidance appears in the supplied text either. The changelog does not say whether existing policies are affected, whether previously configured applications behave differently, or whether any action is required from administrators. The date of the event is not explicitly stated in the evidence. The changelog's own publication timestamp is the only date signal available, and the entry uses relative language, so the exact day the capability became available cannot be confirmed from the supplied material. For a freelancer maintaining security policy for several clients, the sensible reading is that this is an additive configuration capability rather than a change that forces immediate work. The value depends on whether a client's traffic includes destinations that Cloudflare's built-in catalogue does not cover, which is a judgement the changelog does not make for you. The main limitation of this report is its source. Everything above rests on a single vendor changelog entry and the excerpts supplied from it. The linked documentation pages were not provided in full, no independent testing was performed, and no third-party confirmation of behaviour or limits is available in the evidence. That means claims about how the feature behaves in practice, how the improved search and filtering perform, or what the updated metrics show should be treated as vendor statements rather than verified observations. The changelog is authoritative about what Cloudflare says it shipped, and nothing more. The reasonable conclusion is narrow but useful: Cloudflare has documented that custom applications can now be created in the Application Library from hostnames, IP subnets, or both, optionally constrained by TCP or UDP ports or port ranges for HTTP and Network matching, and referenced in Gateway DNS, Network and HTTP policies. Administrators who need that flexibility should read the linked custom applications documentation before relying on the changelog summary alone. ## Key points - Cloudflare's changelog states that custom applications can now be created in the Application Library and referenced in Gateway DNS, Network and HTTP policies. - A custom application is defined by hostnames, IP subnets, or both, according to the changelog. - TCP or UDP ports, or port ranges, can optionally be added to restrict HTTP and Network matching. - The same release covers improved search and filtering in the Application Library, updated interfaces, data and metrics for reviewing applications, and easier selection and management in the Gateway policy builder. - The changelog gives no pricing, plan eligibility, limits, or migration guidance, and the linked documentation pages were not supplied in the evidence. ## Practical implications — editorial interpretation Editorial interpretation: for freelancers and developers who manage Cloudflare One Gateway policies for clients, this is an additive configuration option. If a client's traffic includes internal tools, client-specific endpoints, or subnet ranges that Cloudflare's built-in catalogue does not list, those can now be defined as named applications and reused across DNS, Network and HTTP rules, with optional port or port-range narrowing for HTTP and Network matching. The changelog does not state plan eligibility, limits, or whether existing policies change, so confirm those in the linked documentation before committing to a client rollout. ## Limitations and unknowns The report rests on a single Cloudflare changelog entry and the excerpts supplied from it. The two linked documentation pages were not provided in full, so their operational detail is unknown. No independent testing was performed and no third-party confirmation exists in the evidence. The changelog does not state pricing, plan eligibility, account limits, migration steps, or whether existing policies are affected, and it does not quantify the search, filtering, interface or metrics improvements. The exact availability date is not explicitly stated; only the changelog's publication timestamp is available, and the entry uses relative language. ## Sources - [1] developers.cloudflare.com: Changelog https://developers.cloudflare.com/changelog/post/2026-10-15-app-library-custom-applications/ Retrieved: 2026-10-15T14:17:11.823Z ## Claim references - Cloudflare's changelog says custom applications can be created in the Application Library and referenced in Gateway DNS, Network and HTTP policies. [source 1] - A custom application is defined by hostnames, IP subnets, or both. [source 1] - TCP or UDP ports, or port ranges, can optionally be added to restrict HTTP and Network matching. [source 1] - The release also improves search and filtering in the Application Library and updates the interfaces, data and metrics used to review applications. [source 1] - The release makes it easier to select and manage applications in the Gateway policy builder. [source 1] - The changelog directs readers to documentation on custom applications and on applications and app types for more information. [source 1]