Your backend,

instantly visible for users.

Turn your internal API into UI without frontend development - When API meets YAML, We render UI

고객사로고-온더룩.png고객사로고-맘맘.png리턴잇_공식로고2024_리턴잇 로고 .png11c_kr.pngclassday.png고객사로고-사이즈오브 (1).pngpickleplus.svg파이헬스케어_로고.svg메이크델타로고.pngpotoo (1).svg고객사로고-단길.pngnant.svg

Write spec in YAML, UI follows

If you want to get data from your API, you can add http block (- type: http) and get data by fetch API or axios

- type: http
  method: GET
  fetchFn:

Iterate, iterate, iterate

You can test, deliver, iterate faster ever for internal apps

- type: http
  method: GET # get data from API
  fetchFn:   
- type: http
  params: # add input field for filter
    - key: name
  method: GET
  fetchFn:   
- type: http
  params:
    - key: name
  method: GET
  fetchFn:   
  columns: # clickable column to open modal
    id:
      openModal: modal1
  modals:
    - path: modal1

API fisrt, local first

Stack doesn't matter, your stack is the best choice

You know.. NodeJS, Python, Java, Go, Ruby.. anythings can serve API

You can call local API in our cloud

We know local test saves developers time and makes your brain faster

- type: http
  method: GET
  params:
    - key: name
      placeholder: 검색어를 입력해주세요.  
  fetchFn: |
    const { data } = await axios({
      url: 'http://localhost:9500/items',
      params: {
        q: name || 'all',
      },
    })
    if (data.status !== 200) {
      throw new Error(data.error || 'api error')
    }
    return data.rows

Ready to use out of the box

We love to support you can solve things faster:

Get data from API

- type: http
  params:
    - key: name
    - key: email
  method: GET
  fetchFn:  

Visualize data with Chart library

- type: http
  params:
    - key: name
    - key: email
  method: GET
  fetchFn:
  display: chartjs
  displayFn:

Form best-fit for API server

- type: http
  params:
    - key: name
    - key: email
    - key: file
      format: file
  method: POST
  fetchFn:

Take a look more examples in here!

No overkill. Just the right tool

Skip the complexity, keep the results.