FlagSync home page
Search...
⌘K
Dashboard
Community
Github
Getting Started
Overview
Setup
Types
Flag Evaluation
CLI
Overview
CLI
Client-Side
Overview
JavaScript SDK
React SDK
Server-Side
Overview
Node.js SDK
Next.js SDK
Nest.js SDK
Support
Dashboard
FlagSync home page
Search...
⌘K
Support
Dashboard
Dashboard
Search...
Navigation
Getting Started
Setup
Guides
SDKs
Guides
SDKs
Getting Started
Setup
Get started with FlagSync SDKs for your application.
Getting Started with SDKs
1
SDK Type
Choose client-side or server-side—e.g., web apps may need both for SSR.
Client-Side
For single-user contexts (e.g., web/mobile apps).
Server-Side
For multi-user contexts (e.g., web servers, APIs).
2
Framework Support
FlagSync supports JavaScript in various forms:
JavaScript
React
Node.js
Next.js
Nest.js
Contact
FlagSync Support
for other languages.
3
Security
Use client-side SDK keys for web/mobile apps; keep server-side keys private to protect sensitive flag rules.
Initialization
SDK initialization happens asynchronously—response time, usually 30-50 milliseconds, depends on flag count and ruleset complexity.
Use a singleton pattern to avoid memory leaks—SDKs like Nest.js handle this automatically; others require manual setup.
Creating multiple instances can lead to memory leaks and orphaned connections.
Next Steps
Set up and explore FlagSync SDKs:
Learn SDK differences in
Types
.
Understand evaluation in
Flag Evaluation
.
Start with
Quickstart: SDK
.
Previous
Types
Learn the differences between FlagSync’s client-side and server-side SDKs.
Next
On this page
Getting Started with SDKs
Initialization
Next Steps
Assistant
Responses are generated using AI and may contain mistakes.