Move backend decisions into controlled server-side tools.
WBert lets you keep advanced business rules close to the backend through dynamic C# processes and database functions. The client calls a controlled endpoint, while the server validates security, roles and execution mode before the logic runs.
public static async Task<object> RunAsync(JObject parameters, ProcessContext context)
{
string productId = parameters.Value<string>("productId");
var stock = await context.Db.ExecuteScalarAsync(
"main",
"select count(*) from products where id = @id",
new { id = productId }
);
return new { ok = true, productId, stock };
}
Database functions keep reusable data operations close to the database layer. They can be tested from the platform and then exposed through controlled API endpoints or used internally by processes.
select c.id, c.name, count(o.id) as orders_count, sum(o.total) as total_value from customers c left join orders o on o.customer_id = c.id where c.id = @customerId group by c.id, c.name
Run business logic immediately or move it to a queue.
Not every backend operation should behave the same way. Small operations can run directly and return a result to the client. Longer or more expensive operations can be queued, monitored and reviewed later from the queue calls area.
- Direct mode for quick validations, calculations and service responses.
- Internal queue mode for longer tasks, imports, notifications and background processing.
- Execution history makes completed and failed calls visible to administrators.
Business logic is protected before it runs.
Processes and database functions are not just open scripts. They can be called only through controlled backend paths. The gateway, service keys, user sessions, roles and permissions decide what can execute and under which organization context.
- Role permissions can allow or block specific processes.
- Service-level calls can be separated from normal user calls.
- Special Admin can bypass restrictions, while organizations follow their plan and ACL configuration.
Client stays lighter
The frontend can call a stable API endpoint instead of duplicating backend calculations, validations and data transformations.
Logic evolves server-side
Processes and database functions can be updated in the backend layer as requirements change, without rebuilding every client application.
Operations become visible
Queue calls, test results and execution status help administrators understand what ran, when it ran and whether it failed.
Advanced backend behavior without scattering rules across every client.
WBert centralizes business logic behind secure endpoints, dynamic C# processes, database functions and queue monitoring, giving the client a faster and cleaner path to build application features.