Does my homepage suck?

Overall good. Simple, to the point. My one suggestion would be to spend a little more time explaining exactly how it works. I assumed from context that you store .env files on your secure infrastructure, but you never actually say that on your homepage.

Part of my confusion came from your UI, which is so identical to GitHub that it took me a long time to realize that your screenshot wasn't actually just showing a repo in GH, which didn't make sense. I may be an idiot, but I'd be willing to bet I'm not the only idiot with this problem.

A short intro video that goes through the basic Dotenv Vault workflow would help a lot I think.

In any case, congrats on the launch! This solves a real problem, and you've got a serious tailwind behind you in that hordes of devs already trust and use dotenv (myself included). Good luck!

Hi Mot, I see some of the suggestions already implemented, like the short introduction video, which clears any questions one would have on how exactly it works. 👍

I made a CodePen with all the content and whitespace changes here: https://codepen.io/djsiddz/full/XWEGOGe .

To summarize:

• I've updated the buttons text in the Navbar. This is not very necessary though.
• I gave some importance to the 'Introducing Dotenv Vault' line & dotenv logo. I made the text crisper and added some spacing in the first section.
• I added the 'Latest Versions' heading to make it explicit and reduce the cognitive load on the reader.
• Numbers are significant to create trust, but repeating them isn't necessary, so I cleaned up that section a bit.
• Then, I switched the ordering of the logos of the giants and the text for better context understanding.
• I arranged the Testimonials in small cards to bring some breaks in the continuous lines of text to make it easy to digest. Also left aligned, and added some space above the names of the people.
• Minor text cleanup and highlighting git and cd in the How-to use section
• For the final three buttons at the bottom, I've removed the border-radius to make all buttons on the page have the same style. (I tried experimenting with different border-radius values, but it wasn't looking cohesive with the rest of the website.)
• The 'Sign Up' button has been emphasized to reinforce the call-to-action. I see that the npx dotenv-vault push command is your call-to-action, which is fine, and if it is required, it can be re-iterated here at the bottom instead of the 'Sign Up' button.

Also, I second @me22kar's suggestion to make the header sticky.

P.S. I'm going to start using dotenv-vault right away!

Looks solid to me. Your target audience must be devs, because, well... dark website :P

I would add that your landing page should:

1. State the ultimate benefit ("What's In It For Me")
2. Have one clear CTA

That's it.

In my first software company (sold last year) I started with a two-page blog. My landing page was garbage, but had a simple sign-up form and stated the benefit. When launch occurred, I had a few thousand people on the list and was in profit from day 1.

Keeping it simple is what won the day. Granted, the internet was different 10yrs ago, visual demands are higher now - but the principles are the same. I'm using that same principle on my new software company today and it's paying off (in terms of getting sign-ups).

Looks good, I understand what problems it is solving, but I don't understand how. I am a bit skeptical that using this as a 3rd-party to share .env files is more secure over an e2e encrypted Telegram message, for example.

Looking great. Straight to the point, tells me what you do and how it works in the first 2 sentences.
This byline summed up the problem for me beautifully:

Stop sharing them over insecure channels like Slack and email, and never lose an important .env file again.

We've been using a password manager vault to manage ours but definitely been at places where I've been guilty of sharing like this in the past.

Following the testimonials on the home page it would be cool to see links to some articles highlighting the dangers of sharing this type of information via Slack. I'd say this is how .env files are shared 99% of the time. Slack are a great target for hackers now because of the sensitive data shared there and their messages aren't end-to-end encrypted.

Interesting. I use one of your competitors, https://www.doppler.com/

Personally, I highly value Doppler’s integrations and its many secrets export formats for different services.

In comparison, clicking on your how-to integrations guide for NextJS and Express didn’t work for me. Maybe they are just the same article under a different title. Maybe they don’t exist yet.

Plus, your cli depends on NodeJS, which is a non-starter. I use NodeJS in several places, but I need my secrets to be used everywhere. Installing or bundling NodeJS with the cli is an unacceptable performance penalty.

At the end of the day, I’m already too ingrained into the doppler system to ever consider switching.

Nah your hompage is goat

I think if you go by feature vs benefit, your headline could be more on the lines of "Protect your API keys from getting hacked." or "Even if your websites get hacked, dotenv will makes sure your API keys are always safe."

I dunno. Could be good for a split test.

Hey @mot, I don't think your homepage is suck, it just needs a bit polish with spacing and text size. I would increase the overall text size for headings and body copy to make them easier to read on dark background. Also, the top nav bar should use white text instead of grey.

Hope this could help you!

Generally, it looks pretty slick & clean. But u should definitely work on the paddings a bit more like the paddings between each testimonial, titles "For your team", "For your infra" and so on

It's great and to the point. Fortunately your target segment is already spending hours on the Internet, looking at tools or libraries to improve their workflow.

Your landing page copies are to the point and addressing the problem. The founder's note definitely helps in adding trust. Just a small suggestion- keep the CTAs with a bigger font and button. (the copy to clipboard button in this case.)

Secondly, would also love to see the features on the same page instead of routing to another. You can make the header sticky as well. That way header links are always accessible even when I scroll down.

Everything's great other wise IMO.

I really love this. The concept, UI, and copy all really speak to me.

I'm a dev, and my previous job used hashicorp to send 1 time links for environment variables, which I really never liked. After a transition, I advocated for use of vercel's cli tool which I really really love, and can pull .env variables from remote. Sounds really similar and I LOVE that concept.

Think it looks pretty good. One thing that jumps out to me straight away though is that you might have too many primary CTAs. Try deciding on the main action you want the user to take and focus on that.

Perhaps test reducing it down to focusing on "sign up" — you've described the problem you're solving, and if they're interested in solving that issue, then they can learn more about how to do that once they've signed up.

Not to bad compared to mine lol
mine is very simple (probably too simple)
https://www.writableai.com