SashiDo is an open-source-based Backend-as-a-Service platform built on Parse Server that provides fully managed backend infrastructure for mobile apps, web applications, SaaS platforms, and AI-powered applications.
Unlike proprietary BaaS platforms, SashiDo provides:
It combines the flexibility of open-source infrastructure with the convenience of a fully managed backend platform.
Use a Backend-as-a-Service like SashiDo if you want to build and scale a mobile app without managing servers or infrastructure.
SashiDo provides authentication, database, file storage, and backend logic out of the box, allowing you to launch faster and focus on product development.
👉 See our guide for Best Backend as a Service Providers in 2026
It depends on your app, but Firebase costs can become harder to predict as traffic and usage grow.
Firebase pricing is based on multiple usage factors such as:
Because of this, costs can increase quickly for apps with:
Some teams choose alternatives like SashiDo when they need:
👉 Compare SashiDo vs Firebase in detail
Backend costs vary based on usage, but typically increase as your app grows in traffic, storage, and processing needs.
With SashiDo, you start with a base plan and only pay for additional resources as you scale, making costs more predictable compared to usage-based platforms.
No. SashiDo handles infrastructure, scaling, and maintenance.
You don't need to manage:
This allows you to focus on building your product instead of managing infrastructure.
Yes. SashiDo is suitable for building AI-powered applications and backend services for LLM-based products.
Typical use cases include:
Cloud Code can be used to integrate with OpenAI, Anthropic, or other AI APIs and run AI workflows on the backend.
We also provide 16+ custom GPTs specifically designed to assist with backend development, debugging, and optimization while building your AI app.
Both are Parse Server based platforms, but SashiDo offers more control over scaling and infrastructure.
Key differences:
SashiDo
Back4App
SashiDo is typically preferred for production applications that need scalability and performance control.
👉 Check out the comparison page SashiDo vs Back4app for more details.
The best BaaS depends on your needs, but SashiDo is a strong choice for control, scalability, and long-term flexibility.
Choose based on priorities:
SashiDo stands out with:
👉 Compare SashiDo with other BaaS platforms clicking the respective link above.
Yes. SashiDo is a flexible open-source alternative to Firebase, especially for teams that need more backend control, predictable pricing, and data ownership.
Key differences compared to Firebase:
Many teams migrate from Firebase when they outgrow Firebase's pricing model or need more backend flexibility.
👉 Check out the comparison page SashiDo vs Firebase for more details.
SashiDo is a better fit for mobile apps and backend-driven logic, while Supabase is better for SQL-based web applications.
SashiDo:
Supabase:
Choose SashiDo if: you want backend control, flexible data models, and built-in features for mobile or AI apps.
Choose Supabase if: you prefer SQL and are building a web-first application.
👉 Compare SashiDo vs Supabase in detail
SashiDo includes push notifications as part of your backend, while OneSignal is a separate tool that charges based on users.
The key difference is in pricing and architecture:
Other differences:
Choose SashiDo if: you want predictable costs, backend integration, and full control.
Choose OneSignal if: you need a standalone marketing-focused push notification platform.
Yes. SashiDo is a strong choice for startups building MVPs and scaling to production without managing backend infrastructure.
Startups choose SashiDo because it allows them to:
SashiDo is typically a good fit when:
👉 Learn how to scale your backend as your startup grows
Yes. SashiDo is designed for stable, production-grade applications that require high availability and reliable backend performance.
Enterprise teams choose SashiDo for:
SashiDo is typically used when backend stability, uptime, and predictable performance are critical for the business.
👉 Request a quote for enterprise-grade backend infrastructure by contacting us at support@sashido.io
Yes. SashiDo supports real-time application development through built-in backend features that allow instant data updates and live user interactions.
Key real-time capabilities include:
These features make SashiDo perfect for building:
👉 See how real-time backends are used in modern apps → Best Backend-as-a-Service for Real-Time Data
No. SashiDo is built on the open-source Parse Server stack, which means you always retain full ownership of your:
You can export your entire backend and deploy it elsewhere at any time. We believe customers should stay because the platform is reliable and cost-efficient, not because they are locked in.
👉 See How to Choose a Scalable Backend Platform Without Lock-In
SashiDo is built for long-term reliability, and we have no plans to shut down. We are actively investing in maintaining and improving the platform.
Still, your backend remains portable at all times because SashiDo is built on open-source Parse Server.
You can export your data, files, and Cloud Code and move to another provider or self-host your backend if needed.
SashiDo uses a usage-based pricing model with a base monthly fee and additional charges only for resources you actually use.
Each app fee includes core resources and features like:
You only pay for the resources you use beyond the included limits. There are no forced upgrades, throttling, or hidden enterprise gates.
No. You can add unlimited collaborators to your applications at no additional cost.
SashiDo does not charge per user or per seat, which makes it suitable for growing teams and startups.
The Owner controls billing, subscription, and account-level settings.
Collaborators have full access to build and manage applications, but cannot view or modify billing details.
This setup lets teams work freely, while keeping financial control centralized.
No. SashiDo does not enforce artificial request-per-second limits or throttling.
To handle high traffic and maintain performance, SashiDo gives you control over scalability via the Engines feature. You can increase the number or size of engines to support more requests and ensure consistent response times.
You also have the option to enable autoscaling, which adjusts your backend capacity automatically based on traffic.
Your base plan includes 1M API requests, and any additional usage is charged transparently according to our Pricing.
If you are an application Owner and have added valid billing information, your account will automatically transition to a paid subscription based on the selected hosting region.
If no payment method is added:
If you are a collaborator and no apps are hosted under your account, no charges apply.
It depends, but SashiDo is often more cost-effective as your application grows and requires maintenance, scaling, and reliability. While running your own backend can be cheaper at a very small scale, especially with modern cloud or serverless tools.
However, as your app grows, you need to manage:
SashiDo handles these as part of the platform, so teams can focus on building their product instead of managing backend infrastructure.
SashiDo is typically a better fit when:
We accept the following credit and debit cards:
You can update billing details and payment methods from: Dashboard → Billing
If a payment fails, SashiDo attempts to collect it for 10 days before suspending your applications.
After suspension, your data is kept for a 7-day period and can be restored if payment is completed within this time window.
After this 7-day grace period if no payment is received, applications are permanently deleted
Database recovery may be possible through our Disaster Recovery Service. This is a paid, manual process and depends on technical feasibility. Contact us at support@sashido.io for more details.
If the app is deleted before the next billing date, only the prorated amount for the time it existed will be charged.
Engines are the compute units that power your backend. Think of Engines as the capacity your application has to handle users and requests.
Each Engine provides computing resources used to run:
You can scale your backend by:
You can adjust this at any time and only pay for the capacity you use. This gives you a simple way to control performance and cost without managing servers or DevOps.
SashiDo provides different Engine types depending on your application stage, from development to high-performance production workloads.
You can choose smaller Development Engines for development, testing, staging, and early production, then scale up to Production Engines designed for stable production workloads with higher traffic and background jobs.
You can also choose Performance Engines, which are typically used for heavy workloads, large background jobs, high traffic spikes, and performance-critical applications.
👉 Read more about how to optimize your Engine configuration.
You can scale your backend in three ways, depending on your application's needs:
Vertical Scaling (Scale Up)
Increase Engine size to get:
Horizontal Scaling (Scale Out)
Increase the number of Engines to:
Auto-scaling
You can also take advantage of autoscaling for Production-stage apps, while for development environments, scaling is managed manually.
This combination provides flexible backend scaling without needing DevOps or infrastructure management.
Yes. SashiDo supports autoscaling for production applications, allowing backend capacity to adjust based on traffic.
SashiDo uses Engines to manage backend capacity. You can:
In practice, scaling is hybrid:
This lets you:
The horizontal auto-scaling feature is typically used for Production and Performance Engines, where apps need to handle traffic spikes and growing user bases.
For development environments, scaling is usually managed manually, since autoscaling is not required at that stage.
👉 Learn how SashiDo Engines work
SashiDo's scaling model gives you more control and predictability compared to platforms where scaling happens automatically without providing visibility or control.
Many Backend-as-a-Service platforms handle scaling behind the scenes, which can lead to:
With SashiDo, you can:
This makes it easier to:
This is why SashiDo is a suitable choice for mobile apps, SaaS platforms, AI applications, and high-traffic APIs.
SashiDo uses a flexible scaling model where you can increase backend capacity by adjusting engine size or number.
You can scale manually or use autoscaling to handle traffic changes automatically.
Yes. Every SashiDo application includes direct database connection access. This allows you to:
This is a major advantage compared to some closed Backend-as-a-Service platforms.
Files uploaded through your application are:
The database stores only the URL reference.
This model provides:
It follows industry best practices for modern backend infrastructure.
Files can be uploaded using Parse.File via SDK, REST API or directly through the SashiDo DB Browser.
You do not have direct S3 bucket access. All file operations are handled through the Parse API layer.
Once uploaded:
No. Deleting a database object does not automatically remove the associated file from storage.
To delete files properly, you must:
This ensures clean file lifecycle management and avoids orphaned storage usage.
Here is a detailed tutorial on How to properly delete a file, without leaving an orphan.
The default file upload limit is 20MB per file.
If you require larger file uploads, contact our support team. Dedicated configurations and alternative storage strategies may be available depending on your use case.
Database storage refers to the total structured data stored inside your MongoDB database like app records and user data, while file storage is used for unstructured files uploaded by your application like images and videos.
Database usage impacts:
Editing records does not directly increase storage size, but it counts toward API requests.
SashiDo uses the WiredTiger storage engine for improved performance, compression efficiency, and scalability, while files are stored in a private AWS S3 bucket, separate from your MongoDB database.
This architecture ensures:
Your database stores only the file URL reference, not the file itself.
This separation is considered best practice for scalable mobile and web backends.
Yes. SashiDo provides an Automatic Database Backups feature, which you can enable directly from the Dashboard.
Key details:
This feature ensures business continuity and protects against accidental deletions, migrations, or deployment errors. Read more about the benefits of Automatic DB Backups.
Automatic DB Backups are created once per day during off-peak hours, depending on your hosting region:
Each backup is retained for 30 days. For Dedicated set ups different schedule might be configured. In case you need a custom solution, do not hesitate to contact our team at support@sashido.io.
Yes, if you have created manual backups of your DB previously. Alternatively, if Automatic Database Backups were not enabled, database restoration may still be possible through a manual Disaster Recovery process.
Important details:
We strongly recommend enabling Automatic Database Backups to ensure immediate recovery capability.
You can create manual backups by connecting to your database using the MongoDB connection string from Dashboard → App Settings → Security & Keys. This allows you to export collections in JSON, CSV, or BSON formats using tools like mongodump or MongoDB clients.
You retain full database ownership and export control.
The Parse Server version for each app is displayed below the app name in your SashiDo Account Dashboard.
You can also see and manage your Parse Server version from:
Dashboard → App → Runtime → Parse Server Version
You can upgrade or change versions depending on compatibility and project requirements.
If you require a specific version not present in the Dashboard for compliance, compatibility, or performance reasons, our team can provide guidance and upgrade options for dedicated setups, contact us at support@sashido.io.
You can check your current environment versions by accessing your app's /health endpoint.
You can find your API URL in Dashboard → App Settings → Security & Keys → Application URLs.
Example:
https://your-API-url/health
This is the fastest way to verify compatibility when debugging issues, planning upgrades, or reviewing your backend setup.
Yes. You can install Node.js modules by adding them to your package.json file in your Cloud Code repository.
When you push changes to GitHub, SashiDo automatically installs all dependencies and deploys your application.
This allows you to use:
Yes. You can write your Cloud Code in TypeScript, but it must be compiled to JavaScript before deployment, as SashiDo's Cloud Code runtime executes JavaScript.
You can automate the compilation as part of your deployment process, for example by using an npm postinstall script to run your build command. This allows you to use TypeScript without manually compiling and committing the generated JavaScript files to source control.
👉 Learn more about Cloud Code setup and deployment
Cloud Code lets you run backend logic on SashiDo servers using JavaScript. It is managed through a GitHub repository and automatically deployed when you push changes.
For every application:
You can:
👉 Read more about SashiDo’s built-in GitHub integration for Cloud Code management.
Yes. Push Notifications for iOS and Android are fully supported and ready to use.
The SashiDo Push Notifications Service allows you to:
The service is designed for reliable delivery at scale, helping ensure notifications are processed and sent efficiently even under high load. This makes it suitable for mobile apps, SaaS platforms, and real-time alert systems.
Yes. Both REST and Client Push Notifications are supported.
You can enable them from your SashiDo Dashboard → App → App Settings → Push.
For production applications, we recommend sending push notifications via Cloud Code or REST API, as this provides better control and security.
👉 Learn more about configuring push notifications
Web Push Notifications are not currently supported out of the box.
If this feature is important for your project, you can submit a feature request at hello@sashido.io.
Yes. You can define Background Jobs in your Cloud Code and schedule them directly from the Dashboard.
Yes. Webhooks can be configured directly from the Dashboard.
This makes it easy to integrate SashiDo with third-party services and automation tools.
Yes. You can host static websites and static files by uploading them to the public folder in your Cloud Code GitHub repository.
Yes. SashiDo supports custom domains and free SSL certificates via Let's Encrypt.
You can:
If you already have your own SSL certificate, our team can install it for you upon request.
If logs are not visible, it is usually because console.log is not captured by the logging system.
Use instead:
console.infoconsole.warnconsole.errorIf logs are still missing, contact support for further investigation.
Two-Factor Authentication for the SashiDo Dashboard login is not currently available, but is planned for future implementation.
Yes. You can implement Two-Factor Authentication for your application users using Cloud Code and third-party authentication services.
This allows you to build custom authentication flows, including:
You can submit feature requests straight from the Dashboard or via email at hello@sashido.io, and our team will review them for future implementation.
Feature requests are reviewed and prioritized based on customer demand and product roadmap.
SashiDo's standard pricing plan offers infrastructure across two continents to support global applications and compliance requirements. We are on our own equipment. Current hosting regions include:
You can choose a specific region to host your app based on the majority of your audience's location and benefit from reduced loading speed and improved SEO. You can do a speed test in EU and US or see our benchmark results.
SashiDo also offers fully dedicated, high-performance hosting plans across other regions. These options are ideal for businesses with increasing requirements for security and performance. Contact us at hello@sashido.io for a custom quote.
Each application hosted on SashiDo runs in a separate environment with its own access-controlled database.
Security measures include:
Application owners control who has access to their data, collaborators, and API keys.
This architecture reduces the risk of unauthorized access and ensures application-level data isolation.
Yes. Access Control Lists (ACL) and Class-Level Permissions (CLP) are fully supported via the SashiDo Dashboard.
You can:
This allows fine-grained security control for mobile apps, SaaS platforms, and AI systems.
👉 See how to set up and manage ACLs and CLPs.
Yes. SashiDo's infrastructure is monitored 24/7 using automated monitoring systems and on-call engineers.
Monitoring includes:
This allows the team to detect and respond to infrastructure issues quickly and maintain high platform uptime.
Payments are processed through Braintree, a payment processor that is a validated PCI DSS Level 1 Service Provider, which is the highest level of payment security certification.
All payment data is encrypted and processed through the payment provider. SashiDo does not store full credit card information on its servers.
Yes. SashiDo is GDPR compliant and acts as a data processor under the General Data Protection Regulation.
Application owners using SashiDo are considered data controllers for the personal data of their users.
Personal data related to SashiDo accounts is stored only for the period necessary to provide the services and for legally required retention periods.
👉 You can find more details in our GDPR Privacy Notice.
Yes, if your application processes personal data of users in the European Union, GDPR applies regardless of where your company is based.
As an application owner, you are responsible for:
SashiDo acts as a data processor and provides infrastructure to support compliance, but responsibility ultimately lies with the application owner.
Yes. SashiDo provides the infrastructure and tools necessary to build GDPR-compliant applications, including:
No. SashiDo is not currently HIPAA compliant as a platform.
HIPAA compliance requires specific legal agreements (such as a Business Associate Agreement), strict access controls, and compliance across all infrastructure and service providers involved in handling healthcare data.
SashiDo provides secure infrastructure, but does not currently offer the full set of compliance guarantees required for HIPAA-regulated applications.
If you are building a healthcare application, compliance depends on your overall architecture, including:
👉 Contact our team at support@sashido.io to discuss your specific requirements.
Yes. For customers with higher security or compliance requirements, SashiDo can provide customized infrastructure and security setups, such as:
These solutions are typically used by enterprise customers or applications with strict security and compliance requirements.
If you're interested in such a solution, please send us a note at support@sashido.io, and we'd love to discuss your specific needs in detail.
You can view account login activity from Dashboard → Account → Activity.
If a login occurs from a new IP address, the account owner automatically receives an email notification. This is a standard security measure to detect unauthorized access.
If you want your personal data deleted from SashiDo systems, you can submit a GDPR data deletion request from your Dashboard under the GDPR and Privacy Protection section → Right "to be forgotten".
After you fill out the form, send it to us at support@sashido.io. SashiDo's team will then delete or anonymize personal data in accordance with GDPR.
You can host your application in Europe or North America and run a quick speed test using the links.
Choosing a region closer to your users improves:
For each region, you can check our standard prices here. We can also provide dedicated solutions in different regions. Contact us at hello@sashido.io to get a quote.
Yes. If the app is not yet in production, you can simply create a new app in the desired region and migrate your database, files, and Cloud Code.
If your app is already in production and you need to keep the same App ID, API URL, and credentials, our team can migrate your application to another region.
This process involves manual migration and may have a service fee. Submit a ticket with your request, and our developers will evaluate it and provide an estimated timeline and cost for the migration.
Yes. Some applications run infrastructure in multiple regions for:
If you need a multi-region architecture, contact our team at hello@sashido.io, and we can help design the setup.
Yes. You can migrate from:
Our team can help evaluate and perform the migration as well.
Our Standard support package response time is within one business day. We usually respond much faster during business hours, depending on the complexity of the issue. Faster response times are available with Advanced Support plans.
👉 Learn more about SashiDo's Support Plans.
Every SashiDo application includes Standard Support at no additional cost as per our standard pricing.
Standard Support includes:
This support level is suitable for development, testing, and most production applications.
SashiDo offers two levels of support: Standard and Advanced support.
Standard Support is included with every app and covers:
Advanced Support is designed for mission-critical and production applications and includes:
Advanced Support is typically used by production, enterprise, and business-critical applications.
Advanced Support is recommended if:
For development, testing, early-stage startups, and small to medium non-business-critical apps, Standard Support is usually sufficient.
SashiDo offers multiple support channels, each designed for different types of requests.
You can contact us via:
For technical issues, we strongly recommend using the ticketing system so requests can be properly tracked, prioritized, and handled by engineers.
Yes, as part of the Advanced Support plan.
Advanced Support customers can receive:
This is especially useful for growing SaaS platforms, mobile apps, and high-traffic applications.
Yes. SashiDo monitors infrastructure 24/7 and responds to incidents as they occur.
During incidents, the team handles:
For support response times and services it depends on your plan:
Post-incident reports are provided for major incidents as part of Advanced Support.
👉 Learn more about SashiDo's support plans.
Yes.
Our Status Page shows:
You can subscribe to receive notifications and stay informed about any service-impacting events.
Yes. The SashiDo team can assist with:
Migration and custom infrastructure assistance may be part of Advanced Support or provided as a separate service, depending on the project.
You can find your application API URL in:
Dashboard → App → App Settings → Security & Keys
API requests are all requests made to your application via:
Cloud requests are requests executed inside Cloud Code functions.
Understanding the difference helps you monitor usage and optimize backend performance.
In Metrics → Overview, the database size shown is the maximum database size reached during the current billing cycle, not the current database size.
This is the value used for billing.
To see your actual current database size and daily usage breakdown, go to:
Dashboard → Metrics → Database
Overview metrics are updated daily while other metrics are updated hourly and daily, depending on the metric.
You can check the update interval by clicking the information icon next to each metric.
Only the Owner can delete an application.
To delete:
Dashboard → App → App Settings → Delete This App
This action is irreversible.
Important: Deleting an app does not automatically cancel custom services and services enabled at the Account level, such as:
These must be cancelled separately via the ticketing system, at support@sashido.io, or via the Dashboard, where applicable, to avoid continued charges.
To cancel your account:
Custom services must be explicitly cancelled.
Once processed:
No. Applications consume infrastructure resources even when inactive.
If you want to pause development:
Later, you can:
Note: Deleted applications cannot be restored with the same App ID or URLs.
Yes, but this is not self-service.
Only the current Owner can request a transfer. There must be no unpaid invoices.
Contact support at support@sashido.io or open a ticket, and our team will handle the ownership change.
Account email changes are not available from the Dashboard.
Please contact support at support@sashido.io or open a ticket, and we will update the email address for you.
Start building in minutes
Scale without DevOps
Keep full control of your data