WebSG Custom (Formerly Optical)
Roles & Responsibilities
Overview
How It Works
Features & Roadmap
Getting Started
Roles & Responsibilities
Resources
FAQs

Roles & Responsibilities

Vendor Scope (What Must Be Built on Top of WebSG Custom)

WebSG Custom is a headless backend, your appointed vendor has a substantial build scope:

  • CMS / Schema Configuration: Creating collections, content, fields, approval workflows and relationships within WebSG Custom to fit your agency's content model, and deploying schema, content, roles, media and assets changes from staging into production.
  • Frontend Web Application: Coding, designing and building the public website from scratch (e.g., using Next.js).
  • API Consumption & Page Rendering: Fetching JSON data from WebSG Custom APIs and rendering it into styled web pages, menus, and layouts.
  • Public User Logins & Integrations: Building end-user authentication, dynamic forms, and integrations with external systems or functions.
  • Frontend Application VAPT: Conducting website security testing and remediation specifically for the frontend codebase and custom extensions created by the agency.

 

Component / Responsibility Provisioned by WebSG Custom Platform Built by Appointed Vendor / Agency’s Responsibility
CMS Engine & REST/GraphQL API Gateway ✅ Yes
Dedicated PostgreSQL Database Infrastructure ✅ Yes (Uptime Only)
S3 Asset Storage ✅ Yes
TechPass for CMS Administrators ✅ Yes
WebSG Custom CMS Platform VAPT ✅ Yes
Cloud VA/PT WebSG Custom’s responsibility if frontend is WebSG Custom-hosted Agency’s responsibility if frontend is Agency-hosted
Data Schema & Content Field Setup ✅ Vendor Scope
UI/UX Design, CSS Styling & Visual Templates ✅ Vendor Scope
Public Frontend Codebase (e.g., Next.js) ✅ Vendor Scope
Public User Logins & Custom Integrations ✅ Vendor Scope
Frontend Web Application & Custom Extensions VA/PT ✅ Agency Scope

Last updated 03 Sep 2026

Was this article useful?

A Headless Content Management System that supports Custom Web Capabilities.