Glossary
Use this glossary when a term appears in the AppTego Portal, API, CI/CD integrations, or public documentation.
| Term | Meaning |
|---|---|
| AppTego | The mobile application protection platform used to configure, build, monitor, and automate protected Android and iOS apps. |
| AppTego Portal | Web interface for tenant configuration, protected builds, security dashboards, users, billing, support, and documents. |
| MobileDefender | The AppTego runtime protection component included in protected apps. |
| Protected artifact | The APK, AAB, or IPA produced by AppTego after protection is applied. |
| Source artifact | The original compiled APK, AAB, or IPA uploaded to AppTego for protection. |
| Build job | A portal, API, or CI/CD protection run for one uploaded source artifact. Automation API jobs use a returned job_id; portal and Management API build records are also tied to a build timestamp. |
| Standard Mode | The default integration model where AppTego protects a compiled app without requiring source code changes. |
| Library Mode | Enterprise integration model, also called Custom Library or BYOA, where teams embed a MobileDefender library directly in source code for custom runtime control. |
| Detection control | Runtime control that identifies a threat condition and triggers a configured response action. |
| Prevention control | Runtime or build-time control that blocks or hardens behavior without a separate response action. |
| Response action | The behavior AppTego applies when a detection fires: Log, Terminate, Message, or Redirect, depending on the control and tenant plan. |
| App integrity | Validation that the app, device attestation result, or protected binary state remains trustworthy, including Google Play Integrity and Apple App Attest where configured. |
| Obfuscation | Build-time transformations that make reverse engineering and binary analysis more difficult. |
| Configuration version | The Development, Staging, or Production settings applied to a protected build. API responses use the canonical values development, staging, and production. |
| Promotion | Moving configuration from Development to Staging or from Staging to Production after validation. |
| Deployment environments | Tenant workflow that, when enabled, exposes separate Development, Staging, and Production configuration versions for safer rollout. |
| Live configuration push | Enterprise capability for updating supported runtime settings without rebuilding, when the app was prepared for live updates before release. Build-time controls and structural changes still require a new protected build. |
| Automation API | CI/CD-focused API used to request signed upload URLs, poll protection status, and request signed download URLs for protected artifacts. |
| Management API | Administrative API used to manage portal configuration, users, builds, logs, tenant features, and reporting. |
| Automation key | Raw key_id:key_secret credential used by CI/CD integrations and the Automation API. It is sent as a Bearer token and is not Base64-encoded. |
| API token | Management API credential made from token_key:token_secret, Base64-encoded and sent as a Bearer token with scoped portal permissions. |
| Temporary test signing | AppTego-generated signing used for installable QA builds when no customer signing key is selected. It is not intended for app store distribution. |
| Tenant | An AppTego workspace containing its own apps, users, configuration, builds, logs, subscription, and settings. |