SandboxNEW
Before touching production, test all you want. The sandbox clones your tenant’s environment, configuration and metadata plus the data, into a space fully isolated by design. You try out new objects, automations, processes and layouts without touching what’s live. When you approve, you publish only the changes you want to production, selectively, as a change-set. And best of all: the sandbox doesn’t count toward your bill.
- A full clone of the tenant: configuration, metadata and data in an isolated environment.
- Total isolation by design: nothing from the sandbox leaks into production.
- Selective publishing of changes, the change-set, from the sandbox to production.
Free in Sellio, you only pay for the machine
An isolated test environment is usually a costly enterprise extra. On Sellio the sandbox is part of the product, and it isn’t billed itself: you only pay for your production machine.
Change with no risk to the business
Because the sandbox is isolated by design, you test big changes knowing the production that runs the company is never in danger.
Testing costs nothing extra
The sandbox isn’t billed, so experimenting and validating changes doesn’t weigh on your bill in any way.
Publishing under control
The change-set carries to production only what you approved, keeping unfinished tweaks or tests from escaping to the real environment.
Confidence to innovate
With a safe place to fail, the team tries new objects, automations and processes without the paralysis of fearing they’ll break everything.
The end of changing live
Instead of adjusting production and hoping, you validate first in the sandbox and only push up when you’re sure.
Isolation by design: the sandbox is a separate environment, not a fragile copy inside the same space.
Selective publishing: you choose which changes go up, instead of pushing everything at once.
The sandbox isn’t billed: testing doesn’t grow your bill.
An isolated test environment is usually a costly enterprise-tier feature; on Sellio it’s already included and still free.
Break things freely, far from production
Changing a CRM that runs the business is scary, and rightly so. The sandbox takes that fear away: it clones configuration, metadata and data into an environment isolated by design, where you can break, redo and test without a comma reaching production. What’s live stays untouched while you experiment.
Publish only what passed the test
When the changes are ready and approved, you don’t have to rebuild everything in production by hand. Selective publishing carries only the chosen change-set from the sandbox to the real environment, under control. You decide exactly what goes up, and the rest stays behind.
- 1
Create a sandbox: Sellio clones configuration, metadata and data into an isolated environment.
- 2
Try out objects, automations, processes and layouts freely, far from production.
- 3
Approve the changes that worked and assemble the change-set.
- 4
Publish the change-set selectively to production, at no cost for the sandbox.
Overhauling the sales pipeline
You redesign stages, automations and screens in the sandbox, test with the cloned data and only then publish the new pipeline to production, without interrupting the team.
Testing a risky automation
Before turning on a flow that fires mass emails, you validate it in the isolated sandbox, confirm the behavior and then carry only it to production.
Training without messing up the real base
New users practice in the sandbox with realistic data, learning the system with no risk of scrambling production records.
Is the sandbox billed?
No, the sandbox doesn't count toward your bill, testing doesn't increase what you pay.
Do all sandbox changes go to production?
No, you publish only the change-set you choose, selectively.
What exactly does the sandbox clone?
It clones your tenant's configuration, metadata and data into a fully isolated environment.
If I break something in the sandbox, does it affect production?
No, isolation is by design, nothing from the sandbox leaks into production.
How does selective publishing work?
You choose exactly which approved changes go up as a change-set, instead of pushing everything at once.
Can I test a risky automation before turning it on for real?
Yes, you validate the behavior in the isolated sandbox and only then carry the automation to production.
Can new users train in the sandbox?
Yes, they practice with realistic cloned data with no risk of scrambling production records.
Is a sandbox usually a paid feature elsewhere?
Yes, it's usually a costly enterprise-tier feature; on Sellio it's already included and free.
Do I need to rebuild everything in production after approving it in the sandbox?
No, selective publishing carries the approved change-set straight to production, with no manual rebuild.