> For the complete documentation index, see [llms.txt](https://docs.devcron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devcron.com/welcome.md).

# Welcome

Welcome to our devcron - Professional Website Builder

Related: Web 2.0, Web 3.0

Hi There, My name is Rathakorn Phudithwwanvanits, I am a CEO of devcron.&#x20;

We are the creator of this platform and sell over the world under the exclusive partnership agreement with many others company who are running a SAAS business, webhosting business and also agency.

We are currently operating the business in 4 regions including SEA (Bangkok Head Office, Saraburi - Valley), Pakistan , Televiv (Isarel) and US.

I am very happy that you are here with us and ready to run business with one of the best platform for website builder. We commit all clients to continue our excellence services on our expertise across the world.&#x20;

if you have anything that want our helps on this platform or other service that we offer.

Please feel free to contact me at

{% hint style="info" %}
Email: <rathakorn@devcron.com>
{% endhint %}

I will be ready to help you in any case.

See you soon

Rathakorn Phudithwwanvanits, CEO devcron


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devcron.com/welcome.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
