ไทย
Menu

For procurement · Vendor facts

Everything your procurement team will ask.

Terms, ownership, warranty, legal papers and security practice on one page, so the vendor form takes minutes, not a week of emails.

A general arrangement of a vessel with seven numbered callouts: the bridge for who you contract with, the hold for terms, the anchor for ownership, the plating for warranty, the flag for legal papers, the load line for capacity and the keel for security. FIG. 01 · GENERAL ARRANGEMENT 01 IDENTITY 02 TERMS 03 OWNERSHIP 04 WARRANTY 05 PAPERS 06 CAPACITY 07 SECURITY

01Who you contract with

Legal name
Keel North Software Engineering Co., Ltd.
Registration number
0395569000655
Head office
57/2 Moo 7, Mueang Mai, Si Bun Rueang, Nong Bua Lamphu 39180, Thailand
VAT
Not VAT-registered: quotes carry no VAT
Accountable person
Pinaet Poonsarakhun, founder and lead engineer. The person who scopes your project builds it.

02Commercial terms

Pricing
A fixed price for a written scope, agreed before any code is written. No hourly billing.
Blueprint and Takeover audit
Paid in full upfront. The fee is credited in full to the work that follows within 60 days.
Builds
40% / 40% / 20% at three milestones. Each is signed off at a live demo before you pay it.
Changes
Priced and agreed before they are built: 50% upfront, 50% on delivery.
Care (support)
Monthly, billed quarterly in advance.
Currency
Thai baht. Clients outside Thailand can be quoted in US dollars.
Withholding tax
We accept the 3% withholding on services and your withholding certificate.

03Ownership

Source code
In a repository your organisation owns, from the first day.
Accounts
Domains, cloud, app store and LINE accounts are opened in your name, or moved into it.
IP
The source code and IP of the work you pay for are handed over to you.
Handover
A documented handover pack your team, or another vendor, can work from.

04Warranty and support

Builds
12 months of bug fixes on everything in the scope.
Small products and inherited code
3 months on entry products and on fixes to code someone else wrote.
Care response times
Essential: next business day. Business: 4 business hours. Critical: 1 hour, 24/7 for a system-down incident. Written into the contract.

05Legal papers

NDA
We sign yours, or send ours, before you share anything confidential.
Data processing agreement
Signed on every project that handles personal data, as PDPA section 40 requires of a data processor.
Contract
Your template or ours. The scope, milestones and warranty come from the Blueprint.
Vendor registration
We complete your vendor registration form and send the documents it asks for.

06Capacity and continuity

Builds at a time
At most two, so every project gets the attention it was sold with.
If we were unavailable
Your code, accounts and documentation are already yours, so another team can pick the work up from the handover pack.
Working hours
GMT+7, Monday to Friday, in Thai or English.

07Security practice

What your IT security team or DPO can expect on every project. Ask for the written control list for yours.

  • Reviewed at the startA security and PDPA review is part of every Blueprint, before the build, not at the end.
  • Least accessWe work through named accounts with only the access the work needs, and remove them at handover.
  • No secrets in chatPasswords and keys live in a password manager or secrets store, never in chat, email or the code.
  • Audit logsStaff and admin actions are logged, so you can always answer who changed what.
  • TestedAutomated tests run on every change before it reaches you.
  • Personal dataCollected only where the system needs it, with access by role and a signed data processing agreement.

Found a security problem on keelnorth.com or in something we built? Email [email protected]. We reply within one business day. security.txt

08Documents you can take with you

Need something that isn't here?

Send your form or document list to [email protected] and we will return it within one business day.

[email protected] →