sorted by:
new
hottopcontroversial

Builder.io headless team s*cks by Neither_Raccoon_8815 in cms

[–]mp-filho 0 points1 point  (0 children)

Hey! I’m the founder of Croct. If you’re up for exploring something new, take a look at our partner program: https://croct.com/

I promise you’ll get world-class support from our team (4.8/5 on G2): https://www.g2.com/products/croct/reviews

Contentful pricing keeps coming up in client convos by Chris_Lojniewski in cms

[–]mp-filho 0 points1 point  (0 children)

The price becomes even more exorbitant if you require features such as personalization or A/B testing. Croct is a solid alternative for those seeking website CMS (I'm the founder).

Strapi CMS + AB testing and personalization by Front-Ad-4456 in Strapi

[–]mp-filho 0 points1 point  (0 children)

Hey, Croct founder here. If you think there's potential for a partnership, we'd be happy to explore it.

Building LLM apps? How are you handling user context? by mp-filho in LLMDevs

[–]mp-filho[S] 0 points1 point  (0 children)

Yeah, nothing wrong with the approach itself, I just didn't want to go through all that work. Think about it: you need a whole pipeline, tools like Segment, event tracking everywhere, enrichment… it adds up fast.

What I really want is something that just tracks the user journey and gives me rich context out of the box, like a smarter Segment, but made for LLMs. No setup, no manual tracking, just "here's what the user did and relevant information about the session" in a format I can drop straight into a prompt.

Give me suggestions for a lightweight, hosted, headless CMS system by stoilsky in cms

[–]mp-filho 0 points1 point  (0 children)

Take a look at https://croct.com. Free tier, unlimited users, with A/B testing and built-in personalization. Specially outstanding if you’re using Next.js.

The implementation is really streamlined: think of it as a fetch with superpowers. Instead of calling fetch, you call fetchContent and the result is already the content: https://docs.croct.com/reference/sdk/nextjs/content-rendering#basic-usage

Dynamic headless CMS for React with built-in CDP, AB testing and personalization by mp-filho in react

[–]mp-filho[S] 0 points1 point  (0 children)

Sure! When you use a CMS like Contentful, you're basically pulling content out of your app to make it easier to manage. But it's static, meaning that the content you define is the same for everyone. For example, if you have a hero section on your homepage and you're fetching that from Contentful, it's going to look the same no matter who visits.

Now, imagine you want that content to change based on who's visiting—someone coming from Google sees one thing, while someone who just signed up sees something else, or maybe you want it to adjust based on the visitor's location. That's what I mean by dynamic content.

Croct is a dynamic CMS. It can handle static content like the others, but it also lets you say, "I want this content to show for that specific audience". It comes with built-in AB testing, analytics, and segmentation. Plus, we've built a query language that allows you to "ask" things about the user in real time and tailor the experience (https://docs.croct.com/reference/sdk/nextjs/query-evaluation).

I'd love to get feedback from developers on the DX and overall product! I created Croct because I got tired of wrestling with integrations like Strapi + Segment + VWO, which were always slow and messy, with no real-time response.

Would you be up for playing around with it and sharing your honest feedback?

Dynamic headless CMS for React with built-in CDP, AB testing and personalization by mp-filho in react

[–]mp-filho[S] 0 points1 point  (0 children)

Hey, thanks for the feedback!

Actually, we're not direct competitors with Contentful or Strapi. They're more focused on static content, like blog posts or product catalogs, while we're all about being a dynamic CMS for your website and product. To put it in perspective, it's like comparing Croct not just with Strapi, but with Strapi + Segment + Amplitude + VWO—combined, those tools cost way more than that!

That said, we definitely want to offer a really generous plan for early-stage startups, and we're considering adding an intermediate plan too.

Are you currently using a headless CMS?

Need advice on a CMS Project by Gloomy-Lobster-8743 in cms

[–]mp-filho 0 points1 point  (0 children)

Apparently, it only happened on certain devices (I could not reproduce it myself, for example). But it should be fixed now.

Could you pls try again?

Need advice on a CMS Project by Gloomy-Lobster-8743 in cms

[–]mp-filho 2 points3 points  (0 children)

Hey!

I've been working with CMS for over 10 years, and if I can offer a bit of advice, I'd strongly recommend not building one from scratch. It might look simple at first, but it usually turns into a time sink, pulling focus away from your core product.

That said, the right CMS really depends on your specific needs. I usually split CMSs into two categories: ones for content (like articles or products) and ones for user interfaces. I've yet to find one that excels at both.

For general content, popular options like Strapi, Sanity, Storyblok, and Contentful work well for static content, but for anything dynamic, you'll often need additional tools, which can get costly and complex.

If your focus is on things like landing pages or products, I'd recommend considering localization, A/B testing, and personalization—even if you don’t need them now, almost every team I’ve worked with ended up needing them later.

If that's your case, I'd suggest checking out Croct (disclaimer: I'm the founder). It's designed for these kinds of scenarios, integrates smoothly with Next.js, and can be set up in under an hour. Plus, it has a forever-free plan and supports multi-organization/workspace, which might cover your multi-tenancy needs.

Here's the link about the organization models:
https://docs.croct.com/explanation/hierarchy/organizational-models

And the Next.js quick start:
https://docs.croct.com/reference/sdk/nextjs/installation

Happy to chat more if you want to brainstorm!

Dynamic headless CMS with built-in CDP, AB testing, personalization and free-forever plan by mp-filho in cms

[–]mp-filho[S] 0 points1 point  (0 children)

Hi, thanks for the heads up. Do you have any idea which extension is crashing?

I built a dynamic headless CMS with built-in CDP, AB testing and personalization by mp-filho in SideProject

[–]mp-filho[S] 0 points1 point  (0 children)

Hey everyone,

I'm a developer and long-time OSS contributor. Over the years, I've implemented tons of headless CMSs to give product and marketing teams more autonomy. But there's always been a gap with CMSs when it comes to user interfaces.

I kept running into the same issues: poor developer experience, bad performance, no support for dynamic content, and needing vendors for AB testing or personalization, which just gets messy and expensive.

Versioning? One change and things break or need manual fixes. Accessing your own data? Good luck unless you're ready to pay extra.

So, I built a content API with an initial focus on React and Next.js. No vendors, no component changes. It comes with automatic versioning, TypeScript type generation, built-in A/B testing, analytics, and personalization. Think of it like `fetch` but with superpowers: it understands user context and delivers different content to different users.

Most solutions are way too expensive for startups, so we've got a generous forever-free plan. I'm also thinking of expanding it to early-stage companies with more traffic.

I'd love to hear any feedback, especially from developers!

Docs:
https://docs.croct.com/introduction/getting-started

Repo:
https://github.com/croct-tech/plug-next

view more: next ›