Feature requests - what do you already love, what could be better?

This is an open thread for a discussion re: feature requests!

Please read before commenting.

  • This thread is regularly trimmed to make it more manageable. Posts may be moved or deleted!
  • Responses may be grouped by topic area and moved to a new thread
  • Please review all threads in this category and comment on the most appropriate thread before posting here. :+1:



What could be EVEN BETTER about Netlify products that you use? Have an idea for a killer integration? Share it here! We’re excited to hear all your rad creative ideas and consider things we maybe hadn’t thought were important.

ground rules to keep our engineers sane:

  • This isn’t a Support thread - if you have current issues, please post appropriately elsewhere
  • Please no “i want this too” type responses, use the like button instead
  • Keep it positive - we all get frustrated sometimes, but this is not a vent thread
  • Be Specific - Tell us exactly how changes you are suggesting would improve the product, the workflow, the UI, or whatever you feel could be better! The more time you spend outlining your use case the more likely we are to be able to properly consider your request.

We’re expecting that many of you will share awesome ideas - but we’re expecting that we won’t be able to implement some of them. That doesn’t mean they are bad ideas, but they might not fit with our roadmap. Doesn’t mean you aren’t smart. :smiley:

Off you go!


I would love to be able to upload .SHTML files, or PHP files with simple includes, and have them rendered as HTML. When editing files, I like having the repetitive code (base meta tags, header, nav, footer, etc.) “out of the way” so I don’t have to deal with them. SHTML and PHP make this trivial. It can be done to some extent with jQuery .load(), but page elements tend to jump around on page load. Note that Netlify Snippets don’t really work for this purpose (as handy as snippets are) because any code that exists in a snippet cannot be previewed locally. In other words, I want to be able to build a static site with includes, and have Netlify assemble everything for the visitor. That would be lovely.

1 Like

Some native way to export my Let’s Encrypt SSL certificate & private key would be wonderful, especially as its a wildcard cert. Integrating custom domains with other services often requires this information. In my case, I ran into it attempting to apply a custom domain to my Okta instance.

Without a way to export this information, it means we have to either handle these certificates outside of Netlify, and now we have sprawl in our certificate management, or we have to handle all of our certs outside of Netlify to avoid that sprawl, and now we aren’t getting that benefit out of Netlify.

Of course, using the Let’s Encrypt certs for other services would require us to set up some sort of auto-renewal for the certs ourselves, but if we have to manage our certs outside of Netlify we have to do this anyway. (And, maybe, down the road, Netlify could provide either a. some methodology of allowing integration with the certs they provide even through rotation or b. ssh access to our Netlify instance so we can set up such an integration ourselves).



Since the certificate is issued just to us based on DNS settings, and we don’t have any intention of supplying you with the necessary secret that our system generated to use the certificate, we don’t have any plans to allow export. You can of course fetch your own certificate from lets encrypt by DNS challenge, even at the same time ours is valid :slight_smile:

2 posts were split to a new topic: DNSSEC support on Netlify

I’d love to be able to grab visits via API. Results something along the line of (Shamelessly pinched from BunnyCDN’s log API)

         "cache": "MISS",
         "status": "301",
         "timestamp": "1559138909895",
         "bytes": "521",
         "zone_id": "70112",
         "ip": "x.y.z.0",
         "referrer": "-",
         "url": "https://hosted.fm/",
         "edge": "MI",
         "user_agent": "Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727)",
         "guid": "c81b842ab48d99fbc0e5139d3c2e5b96",
         "country": "US",

Of course with the infrastructure and API in place it would also be possible to have frontend displays of this data too


If only Netlify could also deploy managed Hasura (https://hasura.io/) so that we can deploy apps with database with a great degree of flexibility!


Hook into dynamodb and send email via ses without needing to use your own aws account, just like Netlify


The ability to host a database alongside functions.

Potentially Postgres, or a NoSQL db(?)

I feel this would give users a completed stack across the platform.


3 posts were split to a new topic: Dynamic Image Source Sets

Deployable Naming Convention

I believe a natural extension to the existing branch-specific deployment is to add pattern matching. Given a pattern, such as deploy/* or [deploy]*, all branches meeting that criteria will pass. In doing so, developers can easily deploy staging/*, release/*, support/*, d-feature/* without interruption to workflow or cluttering deployments with all branches.

Accordingly, patterned context names would come before branch-specific names so they can be overridden if necessary. Also, similar to branch-specific deploys, a subdomain equivalent to the star would aid accessibility.



    command = "build command" 

Then, ideally:

My Use Case

In my particular use case, hundreds of collaborator branches may be generated at any given time. Though only a subset of these may require deployment. Being able to add a tag or naming convention enables me to isolate only functional changes.

Prior Inquiry

  1. Automatically deploy branches that match name pattern
  2. Branch Name Pattern Matching

@tcardlab, we do have an open feature request for this and we’ll post an update if/when this feature becomes a reality.


It would be great to be able to quickly see the monthly Build minutes consumed per site.
This would help to quickly identify which sites need to be optimised to reduce total Build minutes.


Hey Jinksi! That’s a really great question - we have an open feature request for this we are working on, as we understand this is a very realistic use case. Thanks for pointing it out!

I will post an update and follow up with you once we have a timeline for this! :muscle:

1 Like

On the DNS page, I would like to be able to set up a set for Google Mail with one click, instead of having manually to enter the five lines of MX information. Namecheap offers this and it’s wonderful.

1 Like

It would be neat to be able to set up catch-all forwarding e-mail address for each site, although that probably would require a server intercepting MX calls. I don’t think this is possible with DNS alone.

DNSSEC is urgently a must.


hi @BayuAngora - we’re already tracking requests for this! We know many people in the community are excited about us implementing DNSSEC. We will update things here as soon as we have anything to share :slight_smile:

1 Like

I would love Rust support. There are multiple static site generators like Cobalt and Zola. Why Rust is better than Node? Cause its fun. I like writing Rust and writing my website in it would be good practice.

Assuming your build process is to clone the entire repo to a jenkins machine and run the build command, the easiest way to achieve this would be to just install cargo on the jenkins VMs. Might need some file access protections and to revoke syscall privileges I dunno. You don’t need to cache common crates until people are building rust generators regularly.

Can I help in any way?