FAQ

Answers to the most commonly asked questions about SCRIPE's architecture, licensing, deployment, and capabilities.

General

What is SCRIPE?

SCRIPE is an enterprise B2B2C SaaS platform that gives your business a fully managed workspace with user management, role-based access, real-time operations, module-based feature expansion, and complete white-labeling capabilities — all in one subscription.

Who is SCRIPE designed for?

SCRIPE is built for development teams and organizations that need to launch enterprise applications quickly without sacrificing architectural quality. Whether you're a startup looking for a scalable foundation, a software house delivering client projects, or an enterprise modernizing legacy systems, SCRIPE eliminates months of foundational boilerplate so you can focus on business logic.

How is SCRIPE different from other ERP platforms?

Unlike traditional ERP systems that lock you into rigid workflows, SCRIPE gives you full source code access with Clean Architecture principles. You get true module isolation (each module can be extracted to its own microservice), built-in multi-tenancy with row-level data isolation, 4 database providers, 7-language i18n with full RTL support, and enterprise security features like the 8-layer security model — all designed to be extended, not just configured.

What industries is SCRIPE suitable for?

SCRIPE is industry-agnostic by design. Its modular architecture allows you to build solutions for healthcare, finance, manufacturing, logistics, education, government, retail, real estate, and more. The core platform provides the common infrastructure (authentication, tenancy, audit, permissions), while business-specific modules can be added or custom-built following the established patterns.

How long does it take to get started?

Getting started with SCRIPE is effortless. Sign up online, and our onboarding team will set up your workspace within 24 hours. Your platform comes pre-configured with all selected modules, user management, and security settings ready to go. Most teams are fully productive from day one.

Technical

What technology stack does SCRIPE use?

The backend is built on ASP.NET Core (.NET 10) with Entity Framework Core, SCRIPE mediator (CQRS), and FluentValidation. The frontend uses Next.js 15 with TypeScript, TanStack Query, Zustand, and a custom design system built on Radix UI. Real-time features are powered by SignalR WebSockets, and the platform supports Docker containerization for deployment.

Can SCRIPE scale from monolith to microservices?

Yes — this is a core design principle. SCRIPE uses strict module boundaries with no cross-module imports. Each module follows Clean Architecture with its own domain, data, and presentation layers. You can start as a monolith for simplicity, move to a gateway topology to separate frontend/backend, and eventually extract individual modules into independent microservices — all without refactoring your code.

What databases are supported?

SCRIPE supports 3 database providers through Entity Framework Core: SQL Server, Oracle, and PostgreSQL. Switching providers requires only a configuration change. Additionally, the Database.Mode setting controls database isolation: 'Single' mode puts all module tables in one shared database, while 'Multi' mode (default) allows each module to have its own database with separate connection strings and even different providers. Each provider has its own migration set, and the platform handles provider-specific quirks transparently.

Can we customize and extend SCRIPE's modules?

Absolutely. You receive full source code access, and every module follows the SOLID View/ViewModel pattern with clear separation of concerns. You can modify existing modules, extend them with new features, or build entirely new modules using the scripe-cli scaffolding tool. The Open/Closed principle ensures you can extend behavior through composition without modifying the core framework.

How does SCRIPE handle database migrations across providers?

Each database provider has its own dedicated migration folder managed by EF Core. When you add or modify entities, you generate provider-specific migrations that account for each database's data types and constraints. The platform includes migration utilities and the CLI can scaffold migrations for all configured providers simultaneously, ensuring consistency across environments.

Licensing

What licensing options are available?

SCRIPE offers flexible licensing tiers designed to scale with your organization. Options include a Starter license for small teams and individual projects, a Professional license for growing companies with advanced features, and an Enterprise license with unlimited deployments, priority support, and custom SLAs. All licenses include full source code access and the right to use SCRIPE in production.

Is there a per-seat or per-user pricing model?

No. SCRIPE uses a per-project licensing model, not per-seat. This means your development team and end-users are unlimited. You pay for the license tier based on features and support level, not the number of developers or application users. This makes SCRIPE particularly cost-effective for organizations with large teams or high user counts.

Can we use SCRIPE for multiple client projects?

This depends on your license tier. The Starter license covers a single project, while Professional and Enterprise licenses support multiple deployments. The Enterprise tier provides unlimited project deployments, making it ideal for software houses and consulting firms that build solutions for multiple clients. Each deployment can be customized independently.

Is there a trial or evaluation period?

Yes. SCRIPE offers a 30-day evaluation period with full access to the platform's features, documentation, and community support. During the trial, you can build a proof-of-concept, explore the architecture, and assess whether SCRIPE fits your technical requirements. No credit card is required to start the evaluation.

What is the upgrade path between license tiers?

You can upgrade your license tier at any time by paying the difference between your current tier and the new one. Upgrades are immediate — you'll receive access to additional features, support channels, and deployment rights as soon as the upgrade is processed. There are no penalties or lock-in periods. Downgrades are handled at renewal time.

Security

How does SCRIPE handle data residency requirements?

SCRIPE is self-hosted, meaning you have complete control over where your data resides. Deploy on your own infrastructure — on-premises, in your preferred cloud region (AWS, Azure, GCP), or in a private data center. The multi-tenancy system supports per-tenant configuration, so you can even host different tenants in different regions to comply with GDPR, HIPAA, or local data sovereignty regulations.

What audit capabilities does SCRIPE provide?

SCRIPE captures audit events from 4 sources: HTTP request logs (every API call with timing and response codes), entity change tracking (who changed what, when, with before/after snapshots), security events (login attempts, password changes, permission modifications), and business operation logs. All audit data is streamable in real-time via SignalR, exportable to CSV/Excel, and supports configurable retention policies.

Does SCRIPE support SSO and external identity providers?

SCRIPE includes a built-in JWT-based authentication system with support for two-factor authentication (2FA), session management, and configurable password policies. The architecture is designed to integrate with external identity providers (OAuth2, OIDC, SAML) through standard ASP.NET Core authentication middleware. Enterprise customers can also integrate with Active Directory, Azure AD, or Okta for single sign-on.

Support

How frequently is SCRIPE updated?

SCRIPE follows a regular release cadence with minor updates every 2–4 weeks and major version releases aligned with .NET and Next.js version cycles. Each release includes detailed changelogs, migration guides, and backward-compatibility notes. Security patches are released as needed, typically within 48 hours of vulnerability disclosure. Enterprise customers receive early access to release candidates.

How does SCRIPE handle breaking changes?

Breaking changes are minimized through SCRIPE's adherence to the Open/Closed principle — new features are added via extension, not modification. When breaking changes are unavoidable (such as major framework upgrades), they are clearly documented with step-by-step migration guides, automated migration scripts where possible, and a deprecation period of at least one major version cycle. Enterprise customers receive dedicated migration assistance.

Can we get help migrating from an existing system?

Yes. Professional and Enterprise license holders have access to migration consulting services. The SCRIPE team can assist with data migration planning, schema mapping, ETL scripts, and phased cutover strategies. For complex migrations, dedicated engineering support is available to accelerate the transition and minimize downtime. Community resources and migration guides are also available for self-service migrations.