The basis we work on: how a quote comes together, who owns the code we write, and what each side can expect of the other.
Last updated
This page governs your use of the Manggala Cloud website and sets the general frame for working with us. By using this site or contacting us through the form, you accept it.
This page is not a project contract. Every engagement runs on its own written proposal, and that proposal is the binding document.
We build websites, web applications, APIs, and internal systems as custom code. Each service is described on the Services pages.
The figures on the Pricing page are starting points for each kind of work, not a binding offer. The final number depends on scope, and we send a written quote after a scoping conversation.
That quote is what sets the scope, the deliverables, the stages, the final price, the payment schedule, the number of revision rounds, and the warranty period. Where the quote differs from this page, the quote prevails.
Amounts and payment schedule are set in the quote you approve, including any payment up front. Unless that quote says otherwise, prices exclude applicable taxes and exclude recurring third-party costs — domains, hosting, subscription services, licensed assets or fonts.
A project keeps to its schedule when both sides hold up their end. On your side that means:
Timeline estimates assume the agreed scope, and assume material and feedback arrive when planned.
Requests beyond the agreed scope can still be done — we tell you what they do to the schedule and the cost first, and the extra work starts only once you approve it.
On full payment, the code and assets we made specifically for your project are yours. We hand over documentation at the end too, so another team can continue the work rather than rebuild it.
Material you supply stays yours. Our internal tooling, generic code, and working knowledge that we carry across projects stay ours — you are not buying exclusive rights to how we work.
We may show launched work as portfolio and case studies, unless you ask us not to. That request is respected: several case studies on this site run without the client's name at the client's request.
Our work uses third-party frameworks, libraries, fonts, and services, each under its own licence. Those licences remain with their owners and do not transfer to you with the project code. Where a paid component is needed, we say so before it is used.
Non-public information you share with us during a project is kept confidential, and we expect the same for the technical detail and pricing we share with you. That obligation outlives the project.
Every engagement carries a bug-fix warranty after launch; its length is stated in your quote. It covers defects in what we built — not new feature requests, not scope changes, and not breakage caused by changes other people make after handover.
We cannot guarantee uninterrupted availability of third-party services outside our control, nor any particular commercial outcome or search ranking. To the extent the applicable law allows, our liability on a project is limited to the amount you have paid for that project, and does not extend to indirect losses.
Either side may end a project with written notice. If that happens, work completed up to that point remains payable, and we hand over what has been paid for in the state it is in.
These terms are governed by the law of the Republic of Indonesia. If a dispute arises we start by talking; failing that, it is settled in the jurisdiction of Semarang, Jawa Tengah.
This page can be updated. The date at the top shows which version applies. A change here does not alter a quote you have already approved — the terms of that quote stand as agreed.
Anything to clear up before we start? Email hello@manggala.cloud — we would rather answer questions about these terms before a quote exists than after.