The free tier has usage caps
The free plan handles 100,000 page visits a day. That's plenty for most organisations, but if your site ever becomes extremely popular you'd need the paid plan at $5 a month, which covers 10 million visits.
Cloudflare Workers' free plan allows 100,000 requests a day. For most community organisations that's more than enough, but high-traffic sites or heavy API use may eventually need the paid plan ($5 a month for 10 million requests).
Free plan can handle 100,000 visitors a day. That's like having your whole kampung visit your site every day, PLUS their friends, PLUS their friends' friends. If you somehow kena more popular than that, the paid plan is only $5 a month. Five dollars. Your kopi-o kosong costs more than that per week.
AI editing isn't perfect
The AI assistant is very capable, but it isn't magic. Sometimes it misunderstands what you want, especially for complex designs. The trick is to be specific and make changes step by step rather than all at once.
Antigravity's AI agent is impressive but not infallible. Complex layouts or very specific design requirements may need manual tweaking. It works best with clear, descriptive instructions and iterative refinement.
The AI very power but not perfect lah. Sometimes it blur like sotong and misunderstands what you want. But same like dealing with real people: just be specific. Say exactly what you want. Don't say "make it nice nice", say "make the header blue with white text". The clearer you are, the better it works.
No traditional CMS
There's no WordPress-style dashboard where you click buttons to change content. Instead, you describe changes to the AI assistant. It's simpler once you're used to it, but it's a different way of working.
There's no WordPress-style admin panel. Content changes happen through code (or by asking the AI to change the code). That's simpler and more secure, but team members used to a CMS may need a short adjustment period.
No WordPress dashboard. No click-this-button-to-add-blog-post interface. Instead, you talk to the AI. Sounds scary at first, but actually way simpler once you try. No more WordPress updates, no more plugin conflicts, no more "your site has been hacked again". Just tell the AI what you want. Done.
A custom domain needs Cloudflare DNS
If you want your website at your own address (like yourorg.org instead of a long Cloudflare URL), you'll need to point your domain to Cloudflare. It's a one-time setup and it's free, but you may want someone technical to help with this first step.
To use your own domain (for example yourorg.org), it needs to be managed through Cloudflare's DNS. That's free, but it involves a one-time change to your domain's nameservers.
Want to use your own domain (like yourorg.com)? Need to point it to Cloudflare. One-time setup only, and it's free. But the DNS thing can be a bit chim, so maybe get your tech-savvy nephew to help for this one step. After that, everything autopilot already.
Some advanced features aren't supported
Node.js runtime constraints
Some advanced programming tools don't work on Cloudflare because it uses a simplified system. This won't affect most websites at all, but it's worth knowing if you ever need very specialised features.
Cloudflare Workers uses a lightweight V8 runtime, not a full Node.js environment. Most things work fine, but some Node.js libraries that rely on filesystem access or native modules won't be compatible.
Some very advanced programming libraries don't work on Cloudflare because it uses a simplified system. But honestly, for 99% of community websites, you won't even notice. It's like complaining that your Toyota Vios cannot go 300km/h: technically true, but when do you ever need to go that fast?
A learning curve for advanced customisation
For everyday changes, the AI handles everything. For very advanced features, like connecting to other services or building complex interactive pages, some technical knowledge helps, or you can ask someone with that background.
The AI handles most tasks, but understanding Astro's component model and Cloudflare's configuration helps with advanced features such as API routes, dynamic server-side rendering or third-party integrations.
For everyday changes, the AI handles everything like a champ. But if you want super advanced features, like connecting to external APIs or building some complex interactive thing, then maybe need someone who knows a bit more. For normal website stuff? The AI got you covered, no worries.