Woke up last week with an amazing SaaS idea, that I validated and already sold to two companies.
Now, I want to simplify my time to market. Here is what I need to create:
Normally, I would code all of it from scratch, but this time I am looking at splitting both into two different sites. I am thinking of the following:
Now, this obviously has some drawbacks, as the frontend and backend will not look identical and that I won't have the ability to customise my frontend with information in regards to if a user is already logged in to the SaaS backend or not.
How do you tackle this or am I overcomplicating it? Adobe combines frontend and backend, Salesforce doesn't, Microsoft combines, Clearbit doesn't, etc.
Any suggestions or thoughts on Pro vs. Con?
It 's really not a big deal to have your saas app on a subdomain. You can host your main site using Wordpress or Ghost and your application on a subdomain like app.example.com I don't think most people even realize there is a subdomain.
For my projects I setup Ghost because its fast and handles SEO and Open Graph tags, sitemap, amp and then the application on a subdomain. On sites that I need everything on the main domain I'll use Ghost for the admin and the Ghost API to display data. (This works great but still took more time than I anticipated)
You should do one
index.phpand call it a day 😛Don't combine.
Spoke to so many founders who regretted it.
The second you want a feature for your website you have to custom code it.
I built https://versoly.com/ to solve it, WP is a huge headache.
site down...
What site?
versoly.com ... it is up now though :).
Interesting do you remember what the error was? We have multiple uptime monitors checking lol and can't see anything our end. Thanks.
It looked as if the server was completely down. But I wonder, where do you host the landing? is it not a S3 or similar? (which could basically never go down).
I see it points to an ec2 instance... who knows maybe it was down for a moment or some DNS issue. But interesting that you do not run it on S3, I guess you have good reasons :).
It is hosted on s3 then served from an ec2 instance. Due to having to serve custom SSL.
Very odd.
Got it. That's a limitation in route53 that is quite disturbing actually.
This comment was deleted 5 years ago
comfirmation bias achieved. thank you!