Congrats on the launch.
What is the difference between this, and say a customized vBulletin et al.? (or, did I misunderstand what the offer is?)
Launch HN: Payload (YC S22) – Headless CMS for Developers
51–60 of 139 posts
Re: Launch HN: Payload (YC S22) – Headless CMS for Developers
#52Was a complete turned off by the original monetization model, what has changed?
Sharp eye - we threw it away and went MIT a few months ago! Basically.... we listened to our audience. And it was a great move. So, thank you for giving us the push if you commented or provided feedback in any way!
That's great to hear!
Re: Launch HN: Payload (YC S22) – Headless CMS for Developers
#53Looks like an interesting idea. Other than PHP-hate, why would someone choose this over something like Drupal?
Personal opinion: Even as someone who used and loved PHP for a decade, Drupal is just awful. It's overengineered and bloated and the documentation is pretty sparse, not to mention it's hard to scale up. Its admin and editor UX is decades being modern headless CMSes. It is extremely powerful, but seemingly built to handle the most extreme edge cases rather than the most common use cases, and a lot of the power is just…
You're not alone.
I ran a team at a weekend hackathon event for non-profits. We needed to finish building their new site on the latest version of Drupal. I had SEVEN devs working on a 5 page brochure site with a page to manage events and we couldn't get it done! I felt terrible leaving it incomplete at the event, but honestly, with Drupal as the tech stack—my hands were tied. Luckily the developer who started the work was able to finish it a few months later.
To do it all over again, I would have convinced them to throw away what they had and use a different platform. If we used any other tech stack, we could have finished and launched the site during the event.
That was the first, and last time I touched Drupal.
Re: Launch HN: Payload (YC S22) – Headless CMS for Developers
#54As someone who's been actively looking for a headless CMS recently, I'm curious about how you compare yourselves to Contentful [1]? From a quick look the key difference is that Payload's backend can be self-hosted, but Contentful is SaaS only. You've said that you're targeting enterprise customers and mention an SLA in that respect. Does that mean your enterprise offering is also SaaS only? [1] https://www.contentful…
Hey there - your points are accurate! Here are a few more: - We are open source / MIT - You can re-use Payload's auth layer in your own apps and with Contentful you can't - Contentful has rigid RBAC, but Payload features function-based access control down to the field level - Payload supports field conditional logic, meaning "check a checkbox, see more fields, uncheck it, extra fields disappear". This is huge. And is…
That is all useful info, thanks.
For the enterprise offering can you give a rough idea of pricing without having to book a demo etc.?
Re: Launch HN: Payload (YC S22) – Headless CMS for Developers
#55We have a Next.js website with a blog section that's powered by Sanity. Problem is, it's pretty finicky to install basic components that we like to use (which looks like Payload comes with out of the box) + communicating with Sanity via groq is clunky with Typescript (and possibly causing some SEO issues).
How simple is it to install Payload in an existing Next.js app to power basically just the /blog/* subdirectory?
Re: Launch HN: Payload (YC S22) – Headless CMS for Developers
#56Earlier quoted context omitted.
Hey there - your points are accurate! Here are a few more: - We are open source / MIT - You can re-use Payload's auth layer in your own apps and with Contentful you can't - Contentful has rigid RBAC, but Payload features function-based access control down to the field level - Payload supports field conditional logic, meaning "check a checkbox, see more fields, uncheck it, extra fields disappear". This is huge. And is…
That is all useful info, thanks. For the enterprise offering can you give a rough idea of pricing without having to book a demo etc.?
Yep! As our cloud hosting is not yet launched, we don't have the pricing finalized for that but for our enterprise features and SLAs, it's all broken down based on what you need. For 20 seats, a few enterprise features and a lower-tier SLA, you'd pay a few thousand a month.
For hundreds of seats, with a more robust SLA, your costs would scale linearly, but it's entirely based on what you need.
Does that help?
Re: Launch HN: Payload (YC S22) – Headless CMS for Developers
#57We have a Next.js website with a blog section that's powered by Sanity. Problem is, it's pretty finicky to install basic components that we like to use (which looks like Payload comes with out of the box) + communicating with Sanity via groq is clunky with Typescript (and possibly causing some SEO issues). How simple is it to install Payload in an existing Next.js app to power basically just the /blog/* subdirectory?
Insanely simple. You can opt-in on a page by page basis with NextJS to any data source that you want to use. I LOVE NextJS' paradigms, and we've actually modeled a lot of what we do after its beautiful DX.
Great question!
Re: Launch HN: Payload (YC S22) – Headless CMS for Developers
#58Earlier quoted context omitted.
Sharp eye - we threw it away and went MIT a few months ago! Basically.... we listened to our audience. And it was a great move. So, thank you for giving us the push if you commented or provided feedback in any way!
That's great to hear!
Seriously, it's liberating to -say-. We're so happy with the move. Credit to the community.
Re: Launch HN: Payload (YC S22) – Headless CMS for Developers
#59> Imagine you're going to build a new SaaS app. Would you think of building it on a headless CMS?
I'm guessing this mostly makes sense for a SaaS that's mostly about serving content to users. I wonder how common that kind of SaaS is, as opposed to a SaaS where the core functionality wouldn't be served well by a CMS, and the administrative tedium that one wants to alleviate mostly has to do with account management, payment processing, enabling or disabling service based on billing status, etc.
Re: Launch HN: Payload (YC S22) – Headless CMS for Developers
#60We have a Next.js website with a blog section that's powered by Sanity. Problem is, it's pretty finicky to install basic components that we like to use (which looks like Payload comes with out of the box) + communicating with Sanity via groq is clunky with Typescript (and possibly causing some SEO issues). How simple is it to install Payload in an existing Next.js app to power basically just the /blog/* subdirectory?
Next.js works great with Payload. One cool feature of Payload is the Local API, which works awesome for server side rendered pages. You get your data from Payload right in your `getServerSideProps` functions.
You'd be interested in the example repo: https://github.com/payloadcms/nextjs-custom-server
The example is set up to manage Pages, but with a few tweaks you'd be able to manage blogs posts instead.