Skip to content
KYAK Coming soon

What is it a good fit for, and what not?

A short checklist before deciding: what the product does well today and what it deliberately leaves out of scope.

Steps

  1. Describe your work in one sentence: which records are kept, who enters them, who approves them?
  2. If it matches an item in the «good fit» list below, look at a similar screen in the demo.
  3. If an item in the «not a fit» list stops you, write it in the request form; we will tell you its roadmap status plainly.
Permission management: roles, groups and users (fictional demo data)
Permission management: roles, groups and users (fictional demo data)

A good fit for

  • Tracking, request, approval and record apps: leave, purchase requests, samples, fixed assets, visit reports.
  • Department records that sit next to the ERP, kept in their own database.
  • Medium-volume data managed with lists, document entry, approvals and dashboards.
  • Data read-only from reporting tools (open to pilot customers).

Scope limit

  • Replacing the ERP: statutory records such as the general ledger, stock costing and payroll stay in the ERP.
  • Issuing official e-Invoice and e-Archive documents: this feature is «In development».
  • Real-time two-way data exchange with external systems: this feature is «Planned».
  • Very high-volume transaction data (thousands of movements per second): the product is not designed for that load.

Features used and their status today

  • In the demoDesigner (Studio)Tables, fields, relations, forms and the menu on one screen; changes stay in draft until you publish.
  • In the demoReady-made lists and documentsEvery table gets a list with search, grouping, column picker and Excel/PDF export; header-and-lines documents with shortcuts matching the ERP you know (Logo, Mega, SAP).
  • In the demoApproval workflowsConditional, multi-step approval for records and documents; pending approvals arrive as notifications.
  • In the demoDashboards and chartsSummary cards and charts from app data; each user arranges their own dashboard.
  • PilotData feed for reporting toolsA read-only feed that respects permissions and personal-data masking; connect from tools such as Power BI.
  • In developmente-Invoicing (Turkey)Generating, sending and tracking e-Invoice and e-Archive documents.
  • PlannedTwo-way integration with external systemsScheduled and event-driven data exchange with other applications.

Other use cases