Skip to main content

NocodilySuite Usage Patterns: How Far to Delegate to the Platform

· About 12 min

NocodilySuite is a platform built from loosely coupled components: authentication (IAM), microservice APIs, storage APIs, admin WebUI, and business WebUI. You can adopt the whole stack, or adopt only part of it and combine the rest with your existing systems or in-house development. Being able to choose the composition based on your organization's situation is what makes real-world adoption feasible. This article covers seven representative composition patterns, each with its fit, benefits, and trade-offs. The spectrum runs from full custom design — defining schema, permissions, and UI yourself — to picking a pre-built catalog that goes live the same day.

Component Overview​

Before the patterns, here are the building blocks. NocodilySuite provisions each of these as part of a per-customer isolated environment.

ComponentRole
IAM (auth API)User management, SSO (SAML 2.0 / OIDC), MFA, RBAC, custom roles, service accounts, token issue / verify
Micromicroservice APICRUD REST APIs auto-generated from schema definitions, with slots for custom logic
Storage APIObject storage with signed URLs and permission control
Admin WebUIConsole for schema, permissions, and operations
Business WebUIEnd-user screens assembled from Form / List / Table / Dashboard components
SDK / OpenAPIClient SDKs and machine-readable specs auto-generated from the definition

Each ships as an independent API or UI, so you can adopt some and combine the rest with your own stack. The patterns below are the most common compositions.

Pattern 1: Full-Stack Adoption​

Composition: IAM + Micromicroservice API + Storage API + Admin WebUI + Business WebUI, all on NocodilySuite.

Fits when​

  • Development resources are limited and you want everything from auth to UI in one stack
  • Launching a new business unit or division with little legacy to integrate with
  • Business staff should assemble and run the system themselves

Benefits​

  • Auth, permissions, API, and UI derive from the same definition, so consistency is structural
  • Changes happen through console operations; no vendor orders needed
  • Initial build lands in weeks to a couple of months, and operations cost is absorbed by the platform

Trade-offs​

  • Business UI is designed within the standard UI component set (Form / List / Table / Card / Dashboard + CSS customization)
  • If you need fine-grained interactions (custom drag-and-drop, advanced animation, etc.), consider Pattern 2 below

Pattern 2: Platform from NocodilySuite, Business WebUI Built In-House on the SDK​

Composition: IAM + Micromicroservice API + Storage API + Admin WebUI on NocodilySuite; business WebUI built in-house with the SDK auto-generated by NocodilySuite, as React / Vue / mobile apps, etc.

Fits when​

  • You want the end-user UI to carry your own interaction patterns and brand design
  • You need multiple clients (mobile apps, embedded devices, etc.) talking to the same API
  • You want to run UI development and API development as parallel tracks

Benefits​

  • SDK and OpenAPI are generated from the definition, so the UI team can start building before the server work is done
  • Auth, permissions, and audit logs stay centralized in the platform; the UI team focuses on business logic and presentation
  • Existing mobile apps and web frontends can integrate through the same API later

Trade-offs​

  • You own the build and maintenance cost of the business WebUI
  • SDK upgrades require client-side follow-up (eased by API versioning)

Pattern 3: Existing IdP + NocodilySuite Platform + In-House Business WebUI​

Composition: Delegate authentication to your existing IdP (Okta / Azure AD / Google Workspace, etc.) via NocodilySuite's IAM. Micromicroservice API + Storage + Admin WebUI stay on NocodilySuite, and the business WebUI is built in-house with the SDK.

Fits when​

  • A mid-sized or larger company that has consolidated authentication on an existing IdP
  • You want employees to avoid remembering new credentials every time a new system is added
  • You want termination, transfer, and MFA to be managed on the IdP side, with the business system just honoring the results

Benefits​

  • Employees sign in to the new system through their existing IdP's SSO
  • Permission changes on termination or transfer propagate automatically via the IdP's lifecycle management
  • Security audits can lean on the existing IdP operation story

Trade-offs​

  • IdP integration (SAML 2.0 / OIDC configuration) must be set up
  • The mapping between IdP roles/groups and NocodilySuite's RBAC needs to be designed up front

Pattern 4: Platform + Admin WebUI from NocodilySuite, Business WebUI In-House​

Composition: IAM + Micromicroservice API + Storage API + Admin WebUI on NocodilySuite; only the business WebUI is built in-house (via SDK). Admin-facing screens use the standard product; end-user-facing screens are custom.

Fits when​

  • The business UI needs significant customization, but the admin UI can use standard features
  • IT admins should manage schema, permissions, and audit logs through a console
  • You want to concentrate UI development effort on the business side

Benefits​

  • No need to build an admin UI; UI effort focuses on the business side
  • IT and operations staff can run admin tasks regardless of how the business UI is built
  • Admin-side permission management, audit logs, and risk analysis come standard

Trade-offs​

  • Admin UI and business UI have separate design systems (business UI doesn't reuse the admin screens)
  • If the same user frequently moves between both screens, SSO bridging needs to be designed

Pattern 5: Headless Platform as an AI Agent Backend​

Composition: IAM + Micromicroservice API + Storage API used headlessly (no UI or minimal UI), with AI agents like Claude calling the APIs directly through an MCP server.

Fits when​

  • You want AI to safely access internal data, but don't need a separate user-facing UI
  • The primary use cases are RAG, data pipelines, or workflow automation via agents
  • You want to layer NocodilySuite's auth + API + storage over existing systems to control AI read/write

Benefits​

  • OpenAPI is auto-generated, so MCP server implementation falls out of the spec naturally
  • AI-driven access is governed by the same RBAC and audit log as user-driven access
  • AI operations are recorded and traceable, which supports compliance and post-incident analysis

Trade-offs​

  • You need to decide up front which APIs are exposed to AI
  • Rate limits, cost ceilings, and prompt-injection safeguards for AI usage are handled by the client-side design

Pattern 6: Catalog Adoption — Fixed-Spec Products, Deployed Same Day​

Composition: Pick a pre-built catalog that packages auth, DB, API, and screens into a ready-to-use product and deploy it as-is. The catalog ships with auth infrastructure, data structure, screens, and operator manuals, so business staff only need to tweak a few settings before going live.

Fits when​

  • The standard catalog design already covers the workflow; no custom design is needed
  • You want the shortest possible time to launch, skipping interviews, design, and development
  • You want to run entirely without development resources
  • The workflow has high cross-industry commonality: inventory, process tracking, customer management, documentation, shift scheduling, etc.

Benefits​

  • Same-day go-live from catalog selection
  • Auth, DB, API, screens, and manuals all come pre-assembled — zero requirements / design work
  • The spec is fixed, so quotes don't vary across vendors and budgeting is clean
  • The backend is provisioned as the same dedicated environment as other patterns, so you can later extend into Patterns 1–5 as needed

Trade-offs​

  • No custom fields or custom workflows in principle — workflows must fit within the catalog's design scope
  • For industry-specific branching or heavy approval flows, Pattern 1 (Full stack) or Pattern 2 (Platform + SDK) is a better fit
  • If catalog mismatch surfaces later, migration to another pattern or parallel operation becomes necessary

Pattern 7: Modernize Authentication for Existing Systems (IAM Gateway)​

Composition: Keep your existing business systems as-is and swap only the authentication layer to NocodilySuite's IAM. The existing systems authenticate via tokens issued by IAM; the existing logic is not touched.

Fits when​

  • The existing system works, but auth is dated (password-only, no SSO, manual termination handling)
  • You don't have the budget for a full rewrite, but authentication infrastructure needs to be modernized first
  • You want this to be the first step in a gradual migration to NocodilySuite

Benefits​

  • You can introduce SSO, MFA, RBAC, and audit logs without large changes to existing system code
  • Auth modernization starts with a modest upfront investment
  • The same foundation can later extend to microservice APIs or storage

Trade-offs​

  • Existing systems need a small change to accept the IAM-issued tokens (usually a middleware addition)
  • The mapping between existing permission models and the IAM's RBAC needs to be clarified first

Required Skills by Pattern​

Pattern selection is driven not just by what you delegate to the platform, but by which skills you have in-house. The table below lays out the roles required inside your organization, and the skills typically covered by GlossVation Inc.'s custom development service when they aren't available in-house.

PatternRequired in-houseSkills typically covered by GlossVation
Pattern 1 (Full stack)Business ownerSchema / permission / screen design assistance, business-logic implementation inside APIs
Pattern 2 (Platform + SDK)Business owner + EngineerBusiness WebUI frontend development (React / Vue / mobile), SDK integration design
Pattern 3 (Existing IdP)Business owner + ITBusiness UI development, IdP integration (SAML 2.0 / OIDC) design, RBAC mapping
Pattern 4 (Platform + Admin UI)Business ownerBusiness WebUI frontend development
Pattern 5 (Headless + AI)Business owner + EngineerMCP server, AI agent development, RAG pipeline implementation, AI governance design
Pattern 6 (Catalog)Business ownerCatalog selection / initial setup assistance, workflow fit-to-catalog support
Pattern 7 (IAM Gateway)Business owner + Engineer + ITToken-acceptance modification on existing systems, permission mapping to RBAC

The business owner is required in every pattern: only someone who actually runs the workflow can correctly translate business rules, org structure, and field semantics into the design. An engineer (a technical point of contact who can guide decisions on frontend, existing-system integration, or AI implementation) and IT (the owner of the existing IdP) are required in-house for the patterns where they appear — to make scoping, acceptance, and operational decisions. The implementation work itself (frontend development, AI implementation, existing-system modification, IdP configuration) is available through GlossVation Inc.'s custom development, so you can select a pattern even when the in-house capacity is partial, scoping only the parts you cannot cover.

Choosing a Pattern​

All seven patterns differ only in where the line sits between the platform-managed parts and the in-house-built parts, and how much of the spec you define yourself. Quick selection guide:

PatternFits when
Pattern 1 (Full stack)Custom-designed for the business, driven end-to-end by business staff
Pattern 2 (Platform + SDK)Business UI needs uniqueness and multi-client support
Pattern 3 (Existing IdP)Enterprise with existing IdP consolidation
Pattern 4 (Platform + Admin UI)Standard admin is fine, only business UI needs custom build
Pattern 5 (Headless)Use as backend for AI agents
Pattern 6 (Catalog)Zero design effort, same-day go-live on a common workflow
Pattern 7 (IAM Gateway)Modernize auth while keeping existing systems

In every pattern, you get IAM, DB, and storage as a per-customer isolated environment. Patterns are not locked in — start with Pattern 6 (Catalog) and move workflows the catalog doesn't cover to Pattern 1, start with Pattern 7 (IAM Gateway) and migrate to Pattern 1, or start with Pattern 1 and replace the UI to move into Pattern 2 — all as your organization evolves.

Support Options When In-House Resources Fall Short​

Regardless of pattern, moments of friction come up — the design gets stuck, existing-system integration runs short on hands, or business-specific logic needs real implementation work. NocodilySuite combines two support options to address these.

Support Console (with a paid plan)​

Depending on your plan, you can send design questions, operational questions, and usage queries directly from the admin console. No separate email thread or chat channel is needed, and the exchange stays on record. This is the right channel for lightweight consultations like:

  • "Does this schema design cover the business requirement?"
  • Permission design and role split questions
  • API usage and error-handling questions
  • Operational best practices
  • Guidance on new features

Custom Development by GlossVation Inc.​

When in-house development capacity is short, or when your business requirements need real implementation work, you can use the custom development service offered by GlossVation Inc. — the company that builds NocodilySuite.

  • Business WebUI implementation: SDK integration with React / Vue / mobile apps (Patterns 2 / 3 / 4)
  • AI agent infrastructure: MCP server implementation, agent development, RAG pipelines, AI usage governance (Pattern 5)
  • Existing-system integration: API integration with core systems, ERP, accounting, and existing SaaS; auth gateway integration (Pattern 7)
  • Existing IdP integration design: SAML 2.0 / OIDC configuration, custom role design, permission mapping (Pattern 3)
  • Business logic inside APIs: Custom code for business-specific aggregation, judgment, branching, and external API calls (all patterns)
  • Schema and permission design assistance: Business-requirement interviews, schema design, permission-model design (all patterns)

As long as a business owner sits inside your organization, everything else can be handled by custom development. "We want to use the NocodilySuite platform but don't have in-house dev capacity" becomes a solvable situation — scope only the parts you cannot cover. You avoid the overhead of selecting a separate development vendor, and a team that already knows the platform's internals handles the work, which structurally reduces black-box risk and spec-drift.

Delegate the heaviest parts first — authentication, microservice APIs, storage — and choose how much of the UI and surrounding pieces to customize based on your situation. That's the composition selection that keeps the cost of building business systems within realistic bounds.