# Daclify roadmap — accounts, DAO deployments and integrations

> Follow Daclify’s roadmap for social and Telegram login, independent DAO contracts, hosted services and future blockchain integrations. Explore the app and handbook.

https://daclify.com/roadmap/

The roadmap builds on a shared workspace for membership, voting, funded work and documents. Here are the next capabilities we want to bring to communities, with availability described in the app’s handbook.

## More ways to join.

Planned account options include social login, Telegram, native wallet linking and managed recovery. Both user-controlled and managed modes need clear explanations of who controls the keys and how recovery works.

### Social and Telegram access — On the roadmap

Make it easier to enter the workspace while preserving one member identity and the DAO’s existing permissions.

### Managed recovery — On the roadmap

Offer a clearly labelled service-assisted mode alongside user-controlled keys, with documented recovery and exit responsibilities.


## Your own contracts, connected to the Hub.

Independent deployments will let a DAO manage its own contracts and upgrades while using the Hub for discovery. This path also needs direct connections, compatible guides and clear operator responsibilities.

- DAO-owned deployment and upgrade control.
- Discovery alongside communities using shared contracts.
- Direct access for communities operating their own infrastructure.

## More support for everyday operations.

Optional hosted services are planned for scheduled actions, notifications and integrations. The goal is less routine administration, with transparent pricing and no change to a DAO’s voting rights.

### Hosted Operations — On the roadmap

Scheduling, Telegram notifications and selected webhooks, with clear limits and permissions.

### Richer governance workflows — On the roadmap

Additional election, committee and proposal-execution options, plus broader project and payroll policies.

### Document access tools — On the roadmap

More complete member key lifecycle, export, retention and recovery workflows.


## Connections beyond one chain.

Telos EVM identities and future payment connections are part of the longer-term direction. Cross-chain payments need verified transaction evidence and clear settlement rules before they can support DAO obligations.

- Treat identity linking and payment settlement as separate capabilities.
- Add integrations for specific community needs.
- Publish supported chains and verification requirements in the handbook.

## Keep the essentials accessible.

Our aim is a useful free governance foundation, with optional paid capabilities for communities that need more. There are no announced prices or delivery dates for roadmap items. The app’s versioned documentation is the reference for supported features.

- Choose tools because they help your community.
- Review feature availability and deployment requirements in the app.
- Share feedback and use cases through the Daclify community.

## Give your community a place to move forward.

Explore DAOs in the app, find the tools your community needs and use the handbook to learn how they work.

- [Open app](https://app.daclify.com/)
- [Read the docs](https://app.daclify.com/docs)
- [Join the community](https://t.me/daclify)