Concepts
Eleven key uKore terms, each with a clear definition and why it matters — written to be cited as-is, with its own anchor so you can link straight to each definition.
uKore isn't (just) a CRM: it's the platform that hosts the CRM as its first app. A business application platform lets you build other apps of your own, beyond the CRM — with their own entities, views and rules — on the same multi-tenant foundation, without writing code.
Why it matters: If your needs grow beyond "managing contacts and deals", you don't need another vendor: you build the app you're missing on the same platform where your CRM already lives.
A configurable CRM is one whose fields, forms, lists and rules can be changed from within the application itself, without depending on an external vendor for every adjustment. In uKCRM, entities and their custom fields are native — not a paid add-on — and forms and lists are schema-driven, editable without a new deployment.
Why it matters: A closed CRM forces you to adapt your process to the software; a configurable one adapts to yours — and that change doesn't depend on waiting for the vendor to ship it.
Multi-tenant means several Organizations (customers) share the same platform, but each one sees and accesses exclusively its own data. In uKore that isolation is applied at the root — every query starts from the Organization that's signed in — and it's verified with dedicated tests that confirm one Organization can never read another's data.
Why it matters: It's the technical guarantee, not just the commercial promise, that your data is kept separate from any other customer's on the same platform.
These are two different things within the ecosystem, and they're licensed differently. A SaaS Module (like uKCRM) is a complete application you subscribe to and activate inside uKore. A Component (like uKReport, uKList or uKForm) is a reusable UI piece, with its own API, that can be used inside a Module or sold directly to a customer as a library — outside the uKore ecosystem.
Why it matters: If you subscribe to a SaaS Module, you're getting a whole app ready to use; if you buy a Component, you're buying a piece for your own development — they're not the same thing, and they're not priced the same way.
The App Builder is the editor you use to create a business app from scratch, without writing code: you define its entities, its fields, its views and its navigation. The app becomes available instantly for your Organization, ready to use and to keep adjusting as your processes change.
Why it matters: You don't need to wait for custom development to get the app your business needs — you build it yourself.
An app template is the installable package of a complete app — its entities, fields, forms, views and navigation — that's installed into your Organization from the uKore Marketplace, and that can be updated later without losing what you've already customized. Before applying an update you can simulate it (dry-run) to see what changes, and if something doesn't fit, roll it back (rollback).
Why it matters: You install a complete app the same day, and when the publisher improves it, you decide whether to apply the change — with the safety of being able to undo it if something goes wrong.
Three field types you don't fill in by hand. A computed field gets its value from a formula over other fields, even a chained one. An auto-numbered field numbers itself, sequentially. A reference field points to a record in another entity and can copy its data when you pick it.
Why it matters: They're the difference between a form you fill in entirely by hand and one that calculates and numbers for you — less work, and fewer data-entry errors.
A view is a different way of looking at the same entity data, without duplicating it. The platform offers four generic views for any entity, your own or installed: list (rows and columns), board (kanban, grouped by state), calendar (records placed by date) and timeline (records as bars you move and stretch over time).
Why it matters: You choose how to work depending on the task — reviewing, managing a process, or planning over time — without anyone having to build each view by hand for every app.
Every record type — a lead, a deal, a task — can have a state workflow: rules for what can happen and when. The system defines which states exist, which transitions between them are allowed, and who's permitted to trigger them — and it checks this on the server before accepting any change, not just on screen.
Why it matters: When you move a card on a kanban board from one column to another, that rule always applies — whether you change it by dragging the card, from a form, or through an integration.
An implementation service — offered by uKodeIT together with uKITAIz, from the same company — that trains an AI model of its own on your project's specific specifications and processes, so your team can ask it questions in natural language. It's always private: it's trained for you, deployed on controlled infrastructure, and your data never trains anyone else's model.
Why it matters: It's not a feature included in uKore — it's a service contracted alongside the implementation, and that distinction is the difference between "a generic chatbot" and "someone who actually knows your project".
LLMO ("LLM Optimization") is to AI discovery what SEO is to classic search: making sure generative engines like ChatGPT, Claude, Perplexity or Gemini can find, understand and cite this site as a source. As part of that practice, this site publishes an llms.txt — a curated Markdown index of its canonical pages — and explicitly allows AI crawlers in its robots.txt.
Why it matters: If you're reading this definition as cited by an AI assistant, that's proof the practice works — you can check the full index at /llms.txt. https://www.ukodeit.com/llms.txt