Cycle is a Git-native delivery platform that helps NetSuite developers ship code safely and precisely in the AI era.
Commit activity
Trusted by NetSuite development teams worldwide
Git-native CI/CD with GitOps-style drift reconciliation, built for NetSuite and SuiteCloud from day one. Not a generic CI pipeline bolted onto SDF.
Keep every NetSuite environment aligned with its branch. Pushed changes sync automatically to NetSuite; File Cabinet changes can be committed to the branch or restored from it.
Deploy complete applications without managing NetSuite objects one by one. SDF projects in each commit deploy automatically to the mapped environment.
Review object changes before one version overwrites another. Cycle compares NetSuite objects with their repository versions and highlights the exact differences.
Securely connect Claude Code or any MCP client to Cycle. Give AI agents live NetSuite context while keeping every change fully controlled, versioned, and auditable.
Code, objects, and releases move through fragmented workflows without a clear change history, making changes slower to ship, easier to overwrite, and harder to maintain and audit.
Without version history, no one knows what changed, who changed it, or why. NetSuite processes become increasingly fragile over time.
When objects are managed manually, changes are difficult to track, and objects can become inconsistent across environments.
Direct changes in NetSuite and separate deployments can create hidden differences that later break functionality or derail releases.
AI agents can make changes in NetSuite faster than teams can review their work, increasing the risk of unintended or untraceable changes.
One source of truth for every NetSuite change
Turn your Git repository into the source of truth for NetSuite delivery. Developers and AI agents work through a single controlled flow: commits deploy automatically, direct NetSuite changes are detected, and drift is reconciled without losing history.
Ten years of customizations and nothing in Git? No problem. Choose what to track from your File Cabinet, and with one click, Cycle creates a baseline commit directly from your NetSuite environment. Your repository starts with what's running today, not an empty folder and good intentions.
Push to Git, and Cycle automatically syncs your changes to NetSuite. If a file changes directly in NetSuite, you see the exact diff so you can commit it back or restore the repository version. No more uploading files and hoping for the best. See what changed, who changed it, and why before anything gets overwritten.
Map branches to NetSuite environments once. Every commit deploys to its mapped environment, while merges promote approved changes across environments. Cycle deploys complete applications exactly as defined in code, so nothing is moved by hand or left behind. What you commit is what gets deployed.
Objects can change directly in NetSuite without developers knowing. Cycle compares each tracked object against its repository version and shows the exact diff before hidden changes disrupt development or derail a release. Commit the NetSuite changes or restore the repository version. You decide what stays.
Connect Claude Code or any MCP client to Cycle. Agents understand what is currently running in each NetSuite environment, so they can build on existing code and objects instead of working blind. With tools like SuiteQL and execution logs, they can investigate issues, diagnose failures, and handle more work on autopilot. Every action remains controlled, versioned, and auditable.
Generating a NetSuite customization with AI can take seconds. Safely deploying and maintaining it in a live ERP is the hard part. Cycle gives your team and AI agents a shared foundation for version control, automated deployments, drift detection, and auditability, so both can move faster without putting production at risk.
Keep your team aligned and your environments under control, with instant clarity into every change.
Connect your NetSuite environments, invite everyone involved, and start with a 14-day Professional trial. No seat limits. No per-user pricing.
No charges until your trial ends — cancel anytime.
Cycle is a Git-native delivery platform for NetSuite. It tracks code and object changes, detects drift between Git and NetSuite, and automates deployments and releases so teams can deliver changes faster and with greater accuracy.
Cycle also lets teams preserve the reason behind each change, creating a reliable history of what changed, why it changed, and how NetSuite evolved. This gives teams, developers, and AI agents the context and guardrails to avoid repeated work and make future changes safely.
Cycle tracks File Cabinet changes and supported NetSuite objects in SDF applications managed through Cycle, including custom fields, custom record types, workflows, forms, saved searches, custom lists, and script records.
When a change is made directly in NetSuite, your team can commit it to the repository or discard it and restore the repository version. Committed changes enter the version history, while the repository remains the source of truth for the tracked files and objects.
Yes. Cycle creates a baseline from the File Cabinet paths you choose to track, so it can begin detecting and reviewing changes from your current NetSuite setup.
You do not need to reorganize everything or convert all customizations to SDF. Existing applications can be migrated gradually, while new applications can use automated SDF deployments from day one.
You need a NetSuite account with SuiteCloud Development Framework enabled, a supported Git repository, and permission to authorize Cycle in both systems.
A NetSuite administrator must configure the Cycle integration application and grant the required permissions for each environment. An authorized repository user must also connect to Git. Your customizations do not need to already be in Git or packaged as SDF applications.
A typical setup takes around 60 minutes. This includes connecting NetSuite and Git, mapping each environment to a branch, selecting the File Cabinet paths to track, and creating the initial baseline.
Accounts with source code outside SuiteScripts or folders containing generated, temporary, or unrelated files may need additional time to configure tracking and exclusions. Once configured, Cycle begins tracking changes immediately.
No. Developers can keep using their current IDEs and NetSuite upload workflows, including VS Code or WebStorm.
Changes made directly in NetSuite can be reviewed and committed through Cycle. Developers can also push commits to feature branches, and Cycle will apply them to the mapped NetSuite environment while Git records the history automatically.
Yes. Your team still controls feature branches, pull requests, naming conventions, approval rules, and release cadence.
Cycle adds a required environment-to-branch structure: each NetSuite environment is mapped to a Git branch, and changes are promoted between environments through those branches. Within that model, your team decides how development and collaboration work.
No. Cycle can track and synchronize File Cabinet changes without requiring your customizations to be packaged as SDF applications.
SDF is recommended when you want to version code and objects together and use repeatable, automated deployments. You can adopt it immediately for new applications and migrate existing ones gradually.
Your Git repository remains the permanent home for your code. Cycle creates only short-lived working copies when it needs to analyze, compare, or deploy changes.
Connections are encrypted in transit, credentials are encrypted at rest, and processing runs in isolated environments. Cycle also uses Cloudflare protection, vulnerability scanning, dependency monitoring, and active security monitoring to reduce exposure and detect potential risks.
Set up in under 60 minutes. Your next push deploys itself.