The first native IDE with AI built in
One native IDE. Now with Claude built in.
Dev Studio is the fully native code editor built inside BOFC — for LWC, Aura, Apex Classes, Triggers, and Visualforce. Now it's the first native Salesforce IDE with an AI model built directly in: ask Claude to write, fix, or explain code, right where your codebase already lives.
Live real-time Sync
4.8/5
AppExchange Rating Verified Admins
50,000+
Teams Already Saving Hours Every Week
100% Native
No Integration Risk. Pure Salesforce.
Zero
Lines of Code. Zero Risk.
100x Faster
Than Manual Profile Recreation
50+
Bulk Metadata Utilities in One App
Everything developers need
Your entire codebase. One console.
Every metadata type a Salesforce developer touches — created, edited,
and deleted from a single native interface.
Lightning Web Components
HTML, JavaScript, CSS, and metadata XML — create, edit, delete.
Aura Components
Controller, helper, style, and markup — all in one editor.
Apex Classes
Browse, write, and edit class logic built for clarity and speed.
Apex Triggers
Every Trigger across your objects, editable without Object Manager.
Visualforce Pages
Manage your Page library and retire what Lightning replaced.
Visualforce Components
View, create, edit, and delete alongside the rest of your codebase.
First of its kind
Meet your new AI pair programmer — built in, not bolted on.
Dev Studio is the first native Salesforce IDE with an AI model working directly inside it. Claude sits alongside every class, trigger, and component you touch, and responds in the same window you're already coding in.
- Write LWC, Aura, Apex, or Visualforce from a plain-language prompt
- Get an instant explanation of any class or trigger you didn't write
- Ask Claude to find and fix an error without leaving the file
- Generate comments and documentation as you go
- Runs inside your existing Salesforce session — your code never leaves the Org boundary
Still struggling with IDEs and extensions to manage your Salesforce code?
Code not syncing properly back to Salesforce?
Forgetting which local changes need to be pushed?
Getting bogged down by legacy, multi-step IDE processes?
Constantly checking with the team about branch conflicts?
Missing manual code retrieval steps?
Battling local CLI or Node.js configuration issues?
Facing stubborn VS Code org authentication errors?
Living with the constant fear of overwriting work?
The Smarter Way to Build:
Welcome to BOFC Dev Studio
Hassle-Free Development
Clean, intuitive, and built specifically for Salesforce teams.
Secure & Native
Keep your entire development lifecycle secure within the Salesforce ecosystem.
Zero Friction
Ditch local environment setup and focus entirely on building great solutions.
Empower your development team. Discover BOFC Dev Studio now!
Apex & Triggers
Edit Apex code without ever leaving Salesforce
- Full support for Apex Classes and Triggers
- Changes save directly to the Org in real time
- No Object Manager hunting for trigger logic
LWC & Aura
Build components live, against your real Org
- HTML, JS, CSS, and XML in a single editor
- Component tree navigation across LWC and Aura
- No context-switch to VS Code to see the change land
Visualforce
Manage Visualforce without the Setup-menu maze
- Full Visualforce Page and Component support
- One searchable library instead of scattered Setup links
- Clean deletion path for pages Lightning has replaced
Static Resources
Manage Static Resources without the Setup-menu maze
- Full Static Resource support
- Search every resource from one place
- Quickly identify and remove unused assets
Why developers love it
Why Salesforce developers love BOFC Dev Studio
Save Setup Time
Skip local installs, CLI auth, and extension updates. Open BOFC and start writing code.
Stay In Control
Full visibility over every piece of custom code, organised and searchable in one place.
Zero Dependencies
No VS Code, no Salesforce CLI, no marketplace extensions to trust or maintain.
Work Without Interruption
What you see is your live Org. Every save lands immediately — no sync cycle to wait on.
The alternative
Salesforce development shouldn't
require local setup
Every other path to writing Salesforce code makes you install,
authenticate, or sync something first. Dev Studio doesn't.
Native
Runs Inside Salesforce
No local install, no CLI, no browser extension. Dev Studio is self-contained inside BOFC, a 100% AppExchange-native app.
Secure
Your Session, Your Security
Authenticated by your existing Salesforce session. Your code never crosses a third-party server or external boundary.
Real-Time
No Sync Cycle
No pull, no push, no waiting. Every change you make in Dev Studio is saved directly to the Org as you work.
Trusted by Salesforce developers
ADMIN OPS CO. NORTHPEAK CONSULTING FIELDWORKS INC CLOUDVERGE ORGSHIFTThe Latest from BOFC v8.3498
This release introduces new capabilities designed to transform how you manage metadata operations, navigate, and build code within Salesforce — Install NOW to get started.
Metadata Studio
- Export Controlling & Dependent Picklist Values
- Clone Classic/Lightning Email Templates
- Export Profile–User–Permission Set Relationships
Dev Studio
- Clone LWC (all files, one click)
- Rename files within LWC/Aura bundles
- Auto-Complete for HTML tags and JS variables/methods
- Syntax highlighting for LWC, Apex, Aura
- Metadata Search (Objects, Custom Settings, Custom Metadata, Labels)
- Claude AI integration for coding, debugging, and comments
What's NEW in this release
Frequently Asked Question
Dev Studio is a fully native code editor built into BOFC. It lets Salesforce developers create, edit, and delete LWC, Aura Components, Apex Classes, Triggers, Visualforce Pages, Visualforce Components, and Static Resources — all from inside their Org, without a separate IDE.
No. Dev Studio ships as part of your existing BOFC installation. Open BOFC and navigate to Dev Studio — there’s nothing new to install or configure.
Yes. Dev Studio is included at no additional cost across every BOFC plan, including the free tier. If BOFC is installed in your Org, Dev Studio is already available.
No. Dev Studio runs entirely within your Org and operates under your existing Salesforce session and security model. There’s no third-party server or external data transfer.
For in-org editing, yes. Dev Studio lets you write and save Apex, LWC, Aura, and Visualforce changes directly to your Org in real time — no local install, no CLI authentication, and no sync cycle to manage.
Changes save directly to your Org as you work. There’s no separate deployment step, no push/pull cycle, and no queue to wait on.
Dev Studio supports the full LWC bundle — HTML, JavaScript, CSS, and the metadata XML — all editable from a single editor.
Yes. Dev Studio supports the full Aura bundle — controller, helper, style, and markup — together in one editor.
Yes. Dev Studio lists every Trigger across your objects in one place, so you can open and edit trigger logic directly without hunting through Setup.
Yes. Both Visualforce Pages and Visualforce Components are supported, searchable in one library — useful for locating and retiring legacy Visualforce that Lightning has replaced.
Yes. Images, JavaScript, CSS, fonts, and ZIP assets are viewable and manageable from one searchable library, making it easy to identify and remove unused resources.
Dev Studio operates within the Org you’re currently authenticated into via BOFC — the same org-based access model used by the rest of BOFC’s features.
Not as such. Dev Studio is built to browse and edit your full codebase — Apex Classes, Triggers, LWC, Aura, Visualforce, and Static Resources — without artificial file limits.
Dev Studio is built for developers working directly with code (Apex, LWC, Aura, Visualforce), so working knowledge of these languages is expected — it’s not an admin point-and-click tool like the rest of BOFC.
Nothing changes. Uninstalling BOFC has no impact on your code — all Apex Classes, Triggers, LWC, Aura Components, Visualforce Pages, and Static Resources remain in your Org exactly as they are. Dev Studio is an editing interface, not a container for your code.
No. BOFC doesn’t attach any namespace or ownership marker to code created or edited through Dev Studio. Anything you write is saved as native, unmanaged code in your Org — indistinguishable from code written any other way.
No. Dev Studio acts purely as a middleware layer — a bridge that gives developers an easier way to work with their Org’s code. It doesn’t own, wrap, or namespace anything you build. The code belongs to your Org, independent of BOFC.
It’s an interface, not a host. Dev Studio doesn’t store a separate copy of your code anywhere — it reads from and writes directly to your Salesforce Org, giving developers a smoother way to work without introducing a new system of record.
