The own-your-software glossary
Plain-English definitions of the words you meet when you own an AI-built or no-code app, each with why it matters to you.
Get started: New here? Start with Understand
In plain English
A quick reference for the terms that show up in tutorials, tool settings, and error messages. Each entry is one sentence plus why it matters to your app. Security terms are written to help you understand risk, not exploit it.
Terms A to Z
Frontend
The part of your app people see and click. It matters because most visible bugs and design changes live here.
Backend
The logic that runs behind the scenes. It matters because rules, calculations, and data handling happen here, out of sight.
API
A way for software to talk to other software. It matters because your app likely uses APIs to send email, take payments, or fetch data.
Database
The organized store for your app's data. It matters because losing or exposing it is the most costly kind of mistake.
Hosting
The service that keeps your app online. It matters because if hosting lapses or misconfigures, your app goes down.
Environment variable
A setting stored outside your code, often for secrets. It matters because it is the safe place to keep keys instead of pasting them into code.
API key / secret
A password-like string that lets your app use a service. It matters because a leaked key can let others spend your money or reach your data.
Dependency
Outside code your app relies on. It matters because outdated dependencies can break your app or introduce security holes.
Deployment
Publishing a new version of your app. It matters because a bad deploy is a common cause of "it worked yesterday."
Backup
A saved copy you can restore. It matters because a tested backup is the difference between a scare and a disaster.
Migration
Moving your app or data to a new place or structure. It matters because doing it carelessly causes downtime or data loss.
Vendor lock-in
How hard it is to leave a tool. It matters because high lock-in limits your choices and leverage.
PII (personal data)
Information that identifies a person, like names or emails. It matters because handling it brings real responsibilities.
Authentication (auth)
How your app verifies who a user is. It matters because weak auth is a common, serious security problem.
Injection
A class of attack where bad input is treated as a command. It matters because AI-generated code sometimes forgets to guard against it; a professional can confirm.
CORS
Browser rules about which sites can call your API. It matters because CORS errors are a frequent, confusing source of "it won't connect."
Rate limiting
Capping how often something can be called. It matters because it protects your app and your bill from abuse and runaway loops.
Row-level security (RLS)
Database rules that decide who can see which rows. It matters because a missing rule can expose everyone's data; verify it with a professional if unsure.
Learn more
- Frontend, Backend, API explained
- Security terms every AI builder should know
- Understand what you built
- Secure what you shipped
- Own your stack
Glossary FAQ
Do I need to memorize these?
No. Use the glossary as a reference when a term comes up. The point is recognition, not memorization.
Are the security definitions enough to secure my app?
They help you understand risk, not eliminate it. For anything touching payments, logins, or personal data, get an independent professional review.
Can you add a term?
Yes. Contact us with the word you keep bumping into and we will consider adding it.
Kodbe is an independent publication about maintaining and owning software you built with AI or no-code tools. It is not affiliated with, endorsed by, or connected to Kodbe Inc (the Albany, GA educational nonprofit), Kodobe, Kodable, or Kodu.