Which open-source tool replaces Calendly Meeting Polls?
For a team that runs group date votes in Calendly Meeting Polls and hits the 40-slot or 40-participant cap, or that wants poll responses off a US-hosted service, the two main self-hosted options are Rallly and Nextcloud Polls. Rallly is a standalone meeting poll tool that ships as a Docker image and lets participants vote without an account, while Nextcloud Polls is an app for organizations already running Nextcloud and is described by its maintainers as similar to Doodle. Calendly Meeting Polls is a poll feature inside a booking product, so the replacement question is narrower than replacing Calendly as a whole.
Licensing differs more than features. Rallly is licensed under AGPLv3 or any later version, and self-hosting is free for personal use with one user. Multi-user instances are asked to buy a license key, with Plus for up to 5 users at $49, Organization for up to 50 users at $499, and Enterprise for 50 or more users from $999 by quote, according to Rallly's licensing documentation. Those keys are perpetual for v4.x and work on an honor system, so an instance keeps running past its limit with an upgrade reminder. Confirm the key terms with Rallly before you commit, and confirm that your server can reach the licensing endpoint over HTTPS. Nextcloud Polls is AGPL-3.0 licensed and carries no per-user fee of its own, but it runs inside Nextcloud, so the cost sits in the server, its maintenance and the staff who run it.
The main gaps are the workflows around the poll. Neither tool offers the routing, reminders and rescheduling that Calendly Meeting Polls lacks in some cases and provides in others, so check each feature you rely on against the vendor's current documentation rather than assuming parity. Nextcloud Polls offers vote limits per option or user, automatic expiry, hidden results and an anonymous mode, which suit surveys with sensitive participation. Rallly offers an availability grid, comments and notifications, and finalizes a chosen date and notifies participants. Test both with a sample poll of your own size before choosing, since the 40-slot and 40-participant limits no longer apply once you self-host.
How Calendly Meeting Polls capabilities map to open-source options
This table maps each Calendly Meeting Polls capability to the closest Rallly or Nextcloud Polls feature, with the gaps noted. Read it as a checklist: where both tools show a gap, confirm the behavior in a test poll on your own server before you commit.
| Capability | Rallly (self-hosted) | Nextcloud Polls (self-hosted) |
|---|---|---|
| Date and time options per poll | Date and time polls with multiple options; confirm the maximum option count for your license tier | Date and time polls; confirm any option cap in your installed version |
| Slot limit (Calendly: 40 slots) | No fixed slot cap is documented in the facts supplied; confirm current limits in the Rallly documentation | Vote limits apply per option or per user; confirm how option counts are handled in your version |
| Participant count (Calendly: 40 participants) | Free for personal use with 1 user; multi-user instances need a license key with tiers of up to 5, 50 and 50 or more users | Participant count depends on your Nextcloud instance and its user base; confirm limits for guest voters |
| Voting without an account | Participants vote without an account; guest voters are not counted against license user limits | Anonymous mode and guest participation are available; confirm the exact guest flow in your release |
| Availability grid | Responses are shown in an availability grid | Results are shown in a voting table; confirm whether it matches the grid view your users expect |
| Comments and notifications | Comments and notifications are supported | Confirm comment support and notification channels in your Nextcloud version |
| Finalizing the chosen time | Organizers finalize a date and notify participants | Confirm how the final option is set and communicated before relying on it |
| Expiry and anonymous voting | Confirm poll expiry options in your version | Automatic expiry, hidden results and anonymous mode are supported |
| Reminders and rescheduling | Not confirmed in the facts supplied; test before relying on it | Not confirmed in the facts supplied; test before relying on it |
Rallly or Nextcloud Polls: which fits which team
Rallly and Nextcloud Polls both replace Calendly Meeting Polls for group date votes, but they sit in different places in your stack. The choice depends on whether you want a dedicated poll tool or a poll app inside a Nextcloud estate you already run and upgrade. The cards below compare licensing, deployment, upgrade work and the features each one covers.
Rallly as a standalone poll tool
Rallly is a dedicated meeting poll product licensed under AGPLv3 or later. It ships as a Docker image, and its stack is Next.js, Prisma, tRPC and Tailwind CSS. Organizers create date and time polls, participants vote without an account, and the organizer finalizes the chosen date and notifies everyone. Choose it when polls are the only job and you want a small, separate service. Confirm the database, container and TLS setup against the project's self-hosting guide before you commit.
Rallly licensing for multi-user instances
Self-hosting Rallly is free for personal use with one user. Multi-user instances are asked to buy a license key, and the honor system means an instance keeps running past its user limit with an upgrade reminder. Keys are perpetual for v4.x and need the server to reach licensing.rallly.co over HTTPS to activate. Plan for the key purchase as a recurring decision, since licensing must be checked against your user count and not just your install date. Ask whether guest voters count toward your limit; unregistered guests do not.
Rallly Spaces for shared poll work
Rallly Spaces, added in v4.3.0, are shared workspaces where members create and manage polls together. Member limits vary by tier, with up to 5, 50 or 100 members per Space on the Plus, Organization and Enterprise tiers. Use Spaces when a department or committee runs recurring scheduling and needs a common list of polls. Check the tier that matches your largest Space before you buy a key, because member counts and user counts are set separately.
Nextcloud Polls inside your Nextcloud
Nextcloud Polls is an AGPL-3.0 app for Nextcloud, which its maintainers describe as similar to Doodle. It adds vote limits per option or user, automatic expiry, hidden results and an anonymous mode. It makes sense if your organization already runs Nextcloud for files and calendars, since it reuses the existing login, sharing and storage. Confirm that the app version is compatible with your Nextcloud major version before you install it.
Nextcloud release cadence and support
Nextcloud publishes a new major version every four months and supports each one for a year through monthly maintenance releases. Nextcloud 35 was released on 16 September 2026 with end of life in September 2027, while Nextcloud 34 is supported until June 2027 and Nextcloud 33 until February 2027. Nextcloud 36 is scheduled for 17 February 2027. Upgrades cannot skip major versions, so you must move one major release at a time, back up first and disable third-party apps until they are confirmed compatible. Budget that work into any Polls decision.
Nextcloud identity and paid support
Nextcloud Server can authenticate users through LDAP and Active Directory, and documents OpenID Connect and SAML backends. Nextcloud GmbH also sells Nextcloud Enterprise with paid maintenance and support tiers, starting with a 100-user minimum. Ask whether your directory integration, support hours and patch lifecycle need a paid tier, or whether your own team can carry them with the community edition. Confirm both choices with the vendor and your security team before you rely on either.
How Rallly license keys change the cost of multi-user use
Rallly is free for personal self-hosting with one user, but a multi-user instance is expected to hold a license key. The tiers in the licensing documentation are Plus for up to 5 users at $49, Organization for up to 50 users at $499, and Enterprise for 50 or more users from $999 by quote. For a team, the cost question is therefore which user cap your headcount falls under, and whether the team will be shared across Rallly Spaces, which allow up to 5, 50 or 100 members per Space depending on the tier. Count the people who will create polls, not everyone who will vote, because guest voters do not count toward the limit.
The licensing model works on an honor system. An instance keeps running past its user limit and shows an upgrade reminder instead of stopping, so the license is a contractual obligation rather than a technical lock. Keys for v4.x versions are described as perpetual, which means a purchase covers the v4 line rather than a recurring subscription. Confirm with Rallly whether that perpetual term carries into any future major version before budgeting for a multi-year rollout. The server must also reach licensing.rallly.co over HTTPS to activate the key, so check that outbound rule with your network and proxy team before go-live, and plan for an air-gapped environment separately.
Before you budget, ask Rallly for written confirmation of current tier prices, the user-counting rules, the terms for perpetual keys across upgrades, and whether a non-profit discount applies, which Rallly offers on request through its support channel. Also confirm how Rallly treats an instance that is cut back to fewer users. The licensing page is the starting point, but it may change, so treat its figures as a snapshot to verify with the vendor.
Running a poll tool beside the rest of the suite
Running Rallly as its own service suits teams that want a group poll tool without changing their calendar setup. Rallly ships as a Docker image, so it can sit beside whatever calendar stack already exists, whether that is Calendly, Microsoft 365 or Google Workspace. Poll options, votes and comments are held by the Rallly instance on your server, and the calendar systems stay outside the poll flow unless your team builds that link and tests it.
- Separate data store: Votes and comments live in the instance you operate, so the poll record does not depend on another vendor's account.
- Finalized times are not placed automatically: Rallly finalizes a chosen date and notifies participants, but the event in each attendee's calendar of record still needs an organizer step or an integration you build.
- A host to patch: Rallly v4.15.5, published on October 18, 2026, was a security release that upgraded Next.js to 16.4.2, so the image needs an owner who tracks releases.
- Licensing by user count: Self-hosting is free for one user, while multi-user instances are asked to buy a license key, so count the people who will organize polls before rollout.
Confirm whether your calendar of record must receive the finalized slot automatically, and run a pilot poll through that path before relying on it.
If the organization already runs Nextcloud, Polls installs as an app on the same server, so polls, files and the Calendar app share one login, one backup set and one upgrade cycle. The upgrade rules apply to the whole server, including Polls, which means the poll tool inherits the server's release calendar and its compatibility constraints. That shared footprint is usually the main reason to choose Polls over a separate service.
- One upgrade path: Nextcloud does not allow skipping major releases, so administrators move one major version at a time, back up before every upgrade and disable third-party apps until they are confirmed compatible.
- Release timing: Nextcloud 35 (Hub 26 Summer) was released on 16 September 2026 with end of life in September 2027, while Nextcloud 33 is supported until February 2027, so check your server's version against the schedule.
- Shared user base: Polls works with the accounts already on the Nextcloud server, so staff who organize polls need no separate account set-up.
- Calendar boundary: Nextcloud Calendar is a separate app from Polls, so confirm whether a finalized poll should create an event there and test that step.
Before scheduling any upgrade, confirm your Nextcloud major version and check that the installed Polls release supports it.
Two standards describe most calendar exchange. iCalendar, defined in RFC 5545 and published in September 2009, is the format for event data. CalDAV, defined in RFC 4791 and published in March 2007, extends WebDAV so that iCalendar-based calendar data can be accessed, managed and shared in a standard way. A poll tool does not have to speak CalDAV to be useful, but knowing which layer handles which job helps when you plan the handoff from a finalized poll to calendars.
- iCalendar as the handoff format: An event exported as an iCalendar file can be imported by most calendar clients, which is the simplest manual route from a finalized poll.
- CalDAV as a sync channel: A server that exposes CalDAV lets clients read and write events, so confirm which calendars your people use and whether they are reachable that way.
- Vendor interfaces differ: Microsoft 365 and Google calendars are often reached through their own interfaces, so CalDAV compatibility is not automatic and should be confirmed with each vendor.
- Invite responses: Attendee replies, updates and cancellations depend on the client and server involved, so test them with real attendees instead of assuming they behave the same.
Ask your calendar administrator which protocol each calendar exposes, and test one finalized poll end to end before rollout.
Sign-in options differ between the two poll tools. Nextcloud documents LDAP and Active Directory integration, where directory users appear in Nextcloud and log in with their directory credentials. Nextcloud also documents OpenID Connect and SAML user authentication backends. Those options control who can organize polls. Participants who vote without an account need no identity set-up at all, since Rallly allows voting without an account and Nextcloud Polls offers an anonymous mode.
- LDAP on the Nextcloud server: Configure the LDAP app in Nextcloud, not in the poll tool, and confirm which directory groups are allowed to log in.
- OIDC and SAML on Nextcloud: Confirm the configured identity provider and how group membership maps to Nextcloud permissions before opening polls to the wider organization.
- Standalone Rallly sign-in: The available information does not establish a directory or single sign-on option for standalone Rallly, so confirm with the vendor before promising staff a unified login.
- Guest votes and licensing: Unregistered guest voters do not count toward Rallly user limits, which affects license planning but says nothing about who may see a poll.
Write down which sign-in method each tool supports in the version you plan to run, and decide whether guest voting is allowed for the data each poll will collect.
Whichever poll tool you choose, the poll and the calendar remain two systems. Votes, comments and the chosen time stay in the poll tool, while calendar holds, reminders and changes after publishing need explicit steps. The Calendly facts are a useful reference point: its Meeting Polls do not support reminders or rescheduling workflows, and slots cannot be added after publishing. Teams that depend on those behaviors should plan them outside the poll tool and confirm how each open-source option handles them.
- Calendar entries: Finalizing a poll does not by itself place events in each attendee's calendar, so confirm the export or integration path for every calendar in use.
- Reminders: Confirm whether each tool sends reminders after finalization and which mail server or relay it uses on your network.
- Changes after publishing: Confirm how each tool handles edits to options or votes after a poll is live, and plan a new poll or a manual update when a meeting moves.
- Availability lookups: Free and busy data from other calendars is not part of a poll unless you configure it, so do not promise availability views until that is tested.
Write down each step from vote to calendar entry, assign an owner to every manual step, and test the full path with a sample poll.
Moving open polls and participant responses to self-hosted tools
This sequence moves active Calendly meeting polls to a self-hosted tool without losing the votes already cast or breaking links participants are using. It ends with polls running on your own server, the chosen time finalized, and every shared link updated.
Inventory open polls and voting windows
The poll owner lists every Calendly meeting poll still collecting responses, with its time options, participant list, invitation links and the date each one is meant to close. Confirm in the Calendly help center, in the Meeting Polls overview, what export of poll results and participant responses is available and whether participant email addresses can be exported, because that determines what you can carry over. Done when you have one register of polls with each poll's status and the data you can take out of Calendly.
Decide which polls to close and which to migrate
For each poll in the register, the organizer decides whether the meeting is already settled, whether the poll is only collecting late votes, or whether it still needs a new round of voting. Polls with a chosen date should be closed in Calendly and the outcome recorded. Polls still needing votes are the only candidates for migration. Done when every poll is marked either close or migrate, with an owner named for each migrated poll.
Confirm the target platform and version
The administrator chooses between self-hosted Rallly and Nextcloud Polls and checks the platform requirements. For Rallly, confirm the release you deploy and the Docker image it ships as in its repository, and note that multi-user instances need a license key under the licensing terms. For Nextcloud Polls, confirm the installed Nextcloud major version against the maintenance and release schedule, since end of life dates differ by version and major upgrades cannot be skipped. Done when the platform, version and support window are written down and the server meets the stated requirements.
Stand up the tool on a supported platform
The platform team installs the chosen tool inside your own infrastructure, sets up the database and TLS, and configures email so that poll notifications reach participants. For Rallly, check that the server can reach the licensing host over HTTPS if you hold a license key. For Nextcloud, take a backup before installing or upgrading and disable third-party apps until they are confirmed compatible. Done when a test poll can be created, voted on without an account and finalized from a clean browser session.
Recreate polls with the full option list
Calendly does not let you add time slots after a poll is published, so each recreated poll must contain every option the group expects from the start. Copy the time options from the register, check the time zone on each one, and add the participant list before publishing. Calendly's limits of 40 time slots and 40 participants do not apply in the new tool, but the organizer should still confirm the maximum for the platform in its documentation. Done when each migrated poll has its complete option list, time zone and invitation text checked against the original.
Run a parallel period with both tools live
For the overlap period, the Calendly poll stays open and the new poll runs alongside it, and the organizer tells participants which link is authoritative. Votes cast in both places are compared each day until participants have moved. Write down any participant who could not vote without an account or who saw a notification error, and fix those issues before cutover. Done when all votes for each migrated poll appear in the new tool and the organizer has signed off on the comparison.
Update shared links and finalize chosen times
Replace the Calendly poll links in calendar invitations, team channels, and any web pages with the new poll URLs, then close each Calendly poll. Once voting ends, the organizer finalizes the chosen time in the new tool, which notifies participants, and records the decision with the outcome. Confirm each closed Calendly poll no longer accepts votes and that the new links resolve for participants outside your organization. Done when no active Calendly poll link remains in use and each migrated poll has a finalized time.
What do buyers ask before replacing Calendly Meeting Polls?
What does it cost to replace Calendly Meeting Polls with self-hosted software?
The software itself is free to download and run. Rallly is licensed under AGPLv3 and Nextcloud Polls under AGPL-3.0, so there are no per-seat license fees for the open-source code. The recurring costs are the server or cloud account that hosts it, the domain, SMTP service for notifications, backups, and the staff time to patch and monitor it. Rallly is free for personal use with 1 user. Multi-user self-hosted instances are asked to buy a license key: Plus for up to 5 users at $49, Organization for up to 50 users at $499, and Enterprise for 50 or more users from $999 by quote, according to Rallly's licensing documentation. If you choose Nextcloud Enterprise for support, its list prices start at 71.29 euros per user per year on the Standard tier with a 100-user minimum, per Nextcloud's pricing page. Ask any implementation partner for a written quote that separates one-time setup from recurring hosting and support.
How long does a Calendly Meeting Polls migration take?
The duration depends on the scope, not on the poll tool itself. Standing up a single Rallly or Nextcloud Polls instance is a small task, but the time grows with the identity integration, the number of users, the email and DNS setup, backup design, and any need to reconcile existing poll history. Calendly Meeting Polls are short-lived, so many organizations run the new tool alongside the old one and switch new polls over after testing. No duration is given here because none has been researched for this scope. Ask for a timeline in the written scope, and confirm which parts depend on your own change approvals and access reviews.
What must our team provide before an implementation starts?
Most of the work depends on access and decisions your team controls. Plan to provide:
- A server or cloud account in your own infrastructure, with OS access and the ability to run Docker (Rallly ships as a Docker image) or the Nextcloud server stack
- DNS control for a poll subdomain and a valid TLS certificate
- An SMTP relay so invitations and notifications are delivered
- The identity source if staff should sign in with corporate credentials, such as LDAP or Active Directory, OpenID Connect or SAML
- Named owners for backups, updates and sign-off on who may create polls
Rallly needs the server to reach licensing.rallly.co over HTTPS to activate a multi-user license key, so confirm that outbound path is allowed.
Can our internal staff run a self-hosted poll tool themselves?
Yes, if you have people who already operate web applications and servers. Rallly is built with Next.js, Prisma, tRPC and Tailwind CSS, and runs as a Docker image, so a team comfortable with containers and reverse proxies can operate it. Nextcloud Polls depends on a Nextcloud server, which means PHP hosting, a supported database, regular upgrades and backups. Nextcloud does not allow skipping major releases, so each upgrade moves one major version at a time, with a backup first and third-party apps disabled until confirmed compatible. Nextcloud 35 was released on 16 September 2026 and is supported until September 2027. Staff need recurring time for these tasks, and that time is the main cost of self-hosting. Ask a partner to document the runbook so the work does not rest on one person.
Can Nextcloud Polls run without an existing Nextcloud installation?
No. Nextcloud Polls is an app for Nextcloud, so it needs a working Nextcloud server before it can be installed. If your organization does not already run Nextcloud, you would deploy the server first, then add the Polls app. Nextcloud All-in-One is the official installation method and bundles caching, PostgreSQL, backups and optional office and talk components, with a Helm chart for Kubernetes. If you only need a standalone poll tool and have no file-sharing use case, Rallly may be the smaller footprint to evaluate. Confirm the Nextcloud server requirements for your chosen version before sizing hardware.
Do Rallly and Nextcloud Polls cover reminders and rescheduling?
Calendly's own help center states that Meeting Polls do not support workflows such as reminders and rescheduling, which is one of the gaps this replacement addresses. Rallly supports comments and notifications, and it finalizes a chosen date and notifies participants. Nextcloud Polls offers vote limits per option or user, automatic expiry, hidden results and an anonymous mode. Neither source in our research confirms automated reminder sequences or a rescheduling workflow for either tool, so ask the maintainers or test in a staging instance before you commit. Your team should decide which reminders are needed and whether they can be handled by the calendar app or by a manual process.
Four trade-offs to weigh before switching
Moving group polls to a self-hosted tool changes more than the hosting location. The four cards below cover what you give up from Calendly's workflow, what you take on operationally, how Nextcloud upgrades constrain your schedule, and how vote limits and features differ between Rallly and Nextcloud Polls. Check each one against your own participant numbers and admin capacity before you pick a tool.
Losing reminders and rescheduling
Calendly Meeting Polls do not support reminders or rescheduling workflows, so the gap is partly a gap you already live with. Rallly sends notifications and finalizes a chosen date with participant notices, but you should confirm exactly which reminder and follow-up messages each tool sends before you rely on them. Plan to handle late changes manually, for example by posting an updated poll or messaging participants directly, and document that process for the people who run meetings.
Running the app yourself
A self-hosted poll tool moves patching, backups, TLS certificates, database maintenance and uptime onto your team. Rallly ships as a Docker image and its recent security release upgraded Next.js, so someone must track releases and apply them promptly. Assign an owner, subscribe to the project's release feed and decide who is on call when a poll link fails before you announce the switch.
Nextcloud upgrades cannot skip releases
If you choose Nextcloud Polls, the app inherits the platform's upgrade rules. Nextcloud does not allow skipping major releases, so each upgrade moves one major version at a time, and you must take a backup before every upgrade and disable third-party apps until they are confirmed compatible. Map this into your change calendar, because a polls rollout on a platform that falls behind can force a multi-step upgrade under deadline pressure.
Vote limits and workflows differ
Calendly caps a poll at 40 time slots and 40 participants, and time slots cannot be added after publishing. Nextcloud Polls offers vote limits per option or user, automatic expiry, hidden results and an anonymous mode, while Rallly licensing depends on user counts and Spaces membership. Test your largest realistic poll with each candidate, confirm how guest voters are counted, and check whether you need hidden results or expiry before choosing.
Keeping poll data and voter identities on your own server
When you self-host Rallly or the Nextcloud Polls app, participant names, email addresses, comments and every vote are written to your own database, not to a vendor's multi-tenant service. That matters most for the people who vote: a colleague's name next to a date they could not attend is personal data, and it stays on servers you operate. Before you go live, decide who can read those records, who holds the database backups, and how long closed polls are kept. Rallly stores its data in the database behind the Docker deployment you run, and Nextcloud Polls stores poll data in the Nextcloud database, so the backup plan for each is the same plan you already apply to that database.
Rallly has one outbound dependency you must plan for. Activating a license key for a multi-user instance requires the server to reach licensing.rallly.co over HTTPS, so a fully air-gapped or egress-restricted host will need a firewall exception or a different arrangement with the vendor. Confirm this with your network team before purchase, and document the single domain in your change record so it is reviewed like any other third-party connection. Keep in mind that license checks concern activation, not the poll content itself, but verify that behavior against the current Rallly licensing documentation rather than relying on this summary.
Nextcloud Polls data is part of the Nextcloud database, so a Nextcloud backup is a poll backup, and a restore is only as good as your last tested restore. Nextcloud requires a backup before every upgrade, so make that backup routine rather than occasional. For both tools, ask the maintainers or the vendor to confirm in writing how long poll data and comments are retained after a poll closes, whether the anonymous or hidden-results mode stops names from being stored or only hides them in the interface, and whether deleted polls remain in backups. Test those answers in a staging instance with dummy voters before you invite real participants.
How DeployOpen scopes and delivers a poll tool replacement
A poll tool replacement touches more than the poll itself: who signs in, which calendars are involved, where the data lives and who keeps it running. DeployOpen agrees these points in a written, fixed scope before any work starts, and the cards below follow that order from scope to ongoing support.
Defining the written scope
The scope sets the poll types needed (date polls, time polls, group availability), the expected number of organizers and participants, and whether polls must be shared across teams. It also records which identity source and calendar systems are in play, so the team can see what is included before the work begins. Ask for the scope to state what is out of scope, such as custom branding, migration of old poll history or email relay setup, so no requirement is left unassigned.
Hosting in your own infrastructure
The Rallly deployment runs as a Docker image in your cloud account, data center or air-gapped network, so poll titles, participant names and votes never leave your servers unless you choose otherwise. Confirm which network paths are open, including outbound HTTPS to licensing.rallly.co if you run a multi-user license key. Agree in writing who owns the host, the container runtime and the database.
Identity and calendar integration
Decide whether organizers sign in with local accounts or with your directory. For Nextcloud Polls, the Nextcloud LDAP app and its OpenID Connect and SAML backends are the documented paths to directory login. For Rallly, check which sign-in options the version you deploy supports before promising them. Agree how calendar free-busy data, if used, will be read and who controls those credentials.
Hardening, backup and upgrades
Hardening covers TLS, administrative access, container isolation, and a patch routine that tracks security releases such as Rallly v4.15.5. For Nextcloud, plan one major version at a time, a backup before every upgrade, and a compatibility check for third-party apps. Backup scope should include the database and attachments, and restores should be tested rather than assumed.
Documentation and compliance evidence
Deliverables typically include an architecture record, runbooks, access lists and backup and restore procedures. DeployOpen prepares systems, controls and evidence for compliance assessments, but it does not issue audit reports, attestations or certifications. Independent auditors and certification bodies make those determinations, so ask early which evidence your assessor expects.
Quotes and optional retainer support
DeployOpen does not publish a price list. A quote follows from the written scope, so the scope should list each component and the responsibilities for each. Ongoing support, upgrades and continuous testing are available as a retainer, which covers work after go-live. Ask any provider to separate one-time build costs from recurring hosting, license and support costs.
