DocsWhen something breaks
What ChimeLab does not do
Worth knowing before you move a site across. If one of these is a dealbreaker, we would rather you found out now than after a migration.
No running backend
ChimeLab serves static output and the frameworks that build to it. There is no Node process, no PHP, no serverless function and no API route running after the build finishes. A front end that talks to an API hosted elsewhere is fine; an app that needs its own server is not, yet. If that is you, talk to us first.
No database
We do not host one, and a static site cannot safely hold the credentials for one anyway. Use a managed database with an HTTP API and call it from the browser with a publishable key.
No edge network
One region, in Indonesia. For an Indonesian audience that is the fastest place to be anyway; for an audience mostly outside the country, a global platform will serve them better.
No per-request metering
Not a limitation so much as a deliberate absence. Nothing is counted per request, per gigabyte or per build minute, so a busy week does not change what you owe — and there is no usage-based scaling to buy either.
One branch per project
A project builds from a single branch, and there are no per-pull-request preview URLs. To preview a branch, create a second project pointed at the same repository.