As I see the default generated envers scheme uses an auto incremented column for revision ID (REVINFO.REV). I assume it would also be possible to use database sequences for that field right?

When the configuration setting org.hibernate.envers.use_revision_entity_with_native_id is true (the default for backward compatibility), then Envers will use an auto-increment database-specific column type. If you set the setting value to false, it will cause Envers to use a Hibernate-based named sequence configured as REVISION_GENERATOR.